Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: linux5.5-5.5.2 (tested on x86_64).
Date: Thu, 06 Feb 2020 13:34:55 +0100	[thread overview]
Message-ID: <20200206123455.UqPwPuibbuVTqgg09K-77WLlfWlZ9Oyhg3i0dtf26po@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18849@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/18849#issuecomment-582885898

Comment:
"You are talking about "without undergoing review", linux5.4 reverted my change to not enable THP by default, as stated in my commit message. Who reviewed this? obviously nobody."

previous mistakes should not justify making them again. Besides, I only call out things I notice problems with, in this case I went to diff the new config against the old one to be able to see what changed so I could use that for the ppc configs.

I don't have an x86_64 machine at hand to test that out, but I had another user on IRC confirm that oldconfig *does not* ask for those things that were changed.

  parent reply	other threads:[~2020-02-06 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18849@inbox.vuxu.org>
2020-02-06  6:50 ` voidlinux-github
2020-02-06  6:54 ` voidlinux-github
2020-02-06  7:18 ` [PR PATCH] [Merged]: " voidlinux-github
2020-02-06 11:50 ` voidlinux-github
2020-02-06 11:53 ` voidlinux-github
2020-02-06 11:59 ` voidlinux-github
2020-02-06 12:03 ` voidlinux-github
2020-02-06 12:09 ` voidlinux-github
2020-02-06 12:12 ` voidlinux-github
2020-02-06 12:12 ` voidlinux-github
2020-02-06 12:13 ` voidlinux-github
2020-02-06 12:13 ` voidlinux-github
2020-02-06 12:14 ` voidlinux-github
2020-02-06 12:34 ` voidlinux-github [this message]
2020-02-06 12:38 ` voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200206123455.UqPwPuibbuVTqgg09K-77WLlfWlZ9Oyhg3i0dtf26po@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).