From: Dave Love <fx@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: why is linux-libre-headers behind linux-libre?
Date: Thu, 02 Nov 2017 10:16:43 +0000 [thread overview]
Message-ID: <87fu9x2df8.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <20171031193852.GB987@macbook41> (Efraim Flashner's message of "Tue, 31 Oct 2017 21:38:52 +0200")
Efraim Flashner <efraim@flashner.co.il> writes:
> On Tue, Oct 31, 2017 at 02:00:35PM +0100, Vincent Legoll wrote:
>> Hello,
>>
>> On Tue, Oct 31, 2017 at 1:35 PM, Dave Love <fx@gnu.org> wrote:
>> > Why is linux-libre-headers a long way behind linux-libre (currently at
>> > version 4.4.47, compared with 4.13.10 for linux-libre)?
>>
>> I suspect this is due to massive rebuilding that would occur when
>> updating linux-libre-headers
>>
>
> This is typically updated in the core-updates branch, but it hasn't been
> updated yet. Based on the LTS versions, we should upgrade it to the 4.9
> branch.
Thanks for the explanations. I checked that 4.9 would support the
Omnipath library, at least.
next prev parent reply other threads:[~2017-11-02 10:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:35 why is linux-libre-headers behind linux-libre? Dave Love
2017-10-31 13:00 ` Vincent Legoll
2017-10-31 19:38 ` Efraim Flashner
2017-11-02 10:16 ` Dave Love [this message]
2017-11-05 15:51 ` Ludovic Courtès
2017-11-06 8:44 ` Mark H Weaver
2017-11-06 8:51 ` Pjotr Prins
2017-11-06 15:18 ` Dave Love
2017-11-06 19:22 ` Mark H Weaver
2017-11-06 21:00 ` Pjotr Prins
2017-11-07 9:56 ` Ludovic Courtès
2017-11-06 15:16 ` Dave Love
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu9x2df8.fsf@albion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).