From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: linux5.5: revamp x86_64 config from linux5.4.
Date: Thu, 06 Feb 2020 15:42:29 +0100 [thread overview]
Message-ID: <20200206144229.s-wZlB6WbdmBGYIVaQTf4cx9q4-2ykUiZI_astp76z8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18852@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/18852#issuecomment-582936893
Comment:
I'm totally against using the "stable" non-LTS kernel as testing grounds for questionable changes. It should follow the same configuration as the LTS trees.
Modules only make sense where 1) it would add too much to size of the kernel 2) it won't be loaded for majority of users.
next prev parent reply other threads:[~2020-02-06 14:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18852@inbox.vuxu.org>
2020-02-06 14:17 ` voidlinux-github
2020-02-06 14:29 ` voidlinux-github
2020-02-06 14:30 ` voidlinux-github
2020-02-06 14:30 ` voidlinux-github
2020-02-06 14:31 ` voidlinux-github
2020-02-06 14:31 ` voidlinux-github
2020-02-06 14:32 ` voidlinux-github
2020-02-06 14:34 ` voidlinux-github
2020-02-06 14:36 ` voidlinux-github
2020-02-06 14:38 ` voidlinux-github
2020-02-06 14:39 ` voidlinux-github
2020-02-06 14:40 ` voidlinux-github
2020-02-06 14:40 ` voidlinux-github
2020-02-06 14:41 ` voidlinux-github
2020-02-06 14:42 ` voidlinux-github [this message]
2020-02-06 14:43 ` voidlinux-github
2020-02-06 14:43 ` voidlinux-github
2020-02-06 14:44 ` voidlinux-github
2020-02-06 14:46 ` voidlinux-github
2020-02-06 14:46 ` voidlinux-github
2020-02-06 14:47 ` voidlinux-github
2020-02-06 14:47 ` voidlinux-github
2020-02-06 14:49 ` voidlinux-github
2020-02-06 14:49 ` voidlinux-github
2020-02-06 14:50 ` voidlinux-github
2020-02-06 15:03 ` voidlinux-github
2020-02-06 15:12 ` voidlinux-github
2020-02-06 15:14 ` voidlinux-github
2020-02-06 15:17 ` voidlinux-github
2020-02-06 15:18 ` voidlinux-github
2020-02-06 15:20 ` voidlinux-github
2020-02-06 15:29 ` voidlinux-github
2020-02-06 15:35 ` voidlinux-github
2020-02-06 15:36 ` voidlinux-github
2020-02-06 15:41 ` voidlinux-github
2020-02-06 15:42 ` voidlinux-github
2020-02-06 15:45 ` voidlinux-github
2020-02-06 15:49 ` voidlinux-github
2020-02-06 15:51 ` voidlinux-github
2020-02-06 16:10 ` voidlinux-github
2020-02-06 16:13 ` voidlinux-github
2020-02-06 16:15 ` voidlinux-github
2020-02-06 16:20 ` voidlinux-github
2020-02-06 16:20 ` voidlinux-github
2020-02-06 17:03 ` [PR PATCH] [Merged]: " 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=20200206144229.s-wZlB6WbdmBGYIVaQTf4cx9q4-2ykUiZI_astp76z8@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).