From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] kernel-libc-headers policy
Date: Sun, 24 Oct 2021 18:02:12 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33729@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33729
Description:
We currently keep kernel-libc-headers stuck to the latest LTS kernel release. Is there any reason we can't update it for each kernel release, besides the time it takes to build cross toolchains?
next reply other threads:[~2021-10-24 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 16:02 ericonr [this message]
2021-11-02 12:18 ` q66
2021-11-04 1:07 ` ericonr
2021-11-04 12:34 ` q66
2021-11-14 1:41 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33729@inbox.vuxu.org \
--to=ericonr@users.noreply.github.com \
--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).