unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: linux-libre updates, timeliness
Date: Mon, 05 Oct 2020 15:53:05 +0200	[thread overview]
Message-ID: <87imboye2m.fsf@gnu.org> (raw)
In-Reply-To: <20200930224538.GA20730@jasmine.lan> (Leo Famulari's message of "Wed, 30 Sep 2020 18:45:38 -0400")

Hi Leo,

Leo Famulari <leo@famulari.name> skribis:

> I just pushed commit 51eb3e11 [0], bringing our linux-libre kernel
> packages up to date.
>
> It's September 30 here. The commit is dated September 28, because that's
> when I made it. These kernels were released upstream on September 26. 

Of course we can always do better, but I think 4 days is reasonable.

> Personally, I am okay with the risks implied by this kind of timeframe,
> but as a distro we should try to do these updates more quickly. Ideally,
> they should be updated as soon as the sources are available and the
> packager has tested the changes. I am committed to helping maintain the
> linux-libre packages, but I won't always update our packages right away.
>
> Everyone can contribute here! Minor linux-libre kernel updates can be
> relied upon to work. They almost never cause blocking problems, based on
> the lack of bug reports about them.

What update, build, and testing recipe would you recommend to someone
willing to help?

Thanks for your work, much appreciated!

Ludo’.


  reply	other threads:[~2020-10-05 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 22:45 linux-libre updates, timeliness Leo Famulari
2020-10-05 13:53 ` Ludovic Courtès [this message]
2020-10-05 21:12   ` Yasuaki Kudo
2020-10-06 14:48     ` Leo Famulari
2020-10-06 21:32       ` Yasuaki Kudo
2020-10-09 19:54         ` Leo Famulari
2020-10-06 14:49   ` Leo Famulari

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=87imboye2m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).