unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Attila Lendvai <attila@lendvai.name>,  Guix Devel <guix-devel@gnu.org>
Subject: Re: cirrus (was Re: Release progress, week 10)
Date: Sun, 18 Dec 2022 17:27:52 +0100	[thread overview]
Message-ID: <87bko0vfqv.fsf@pelzflorian.de> (raw)
In-Reply-To: <87v8m8g30u.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 18 Dec 2022 16:11:45 +0100")

Ludovic Courtès <ludo@gnu.org> writes:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>> That hold-up aside, maybe could you also tentatively add the cirrus
>> initrd module to the 1.4.0 installation image?  I suppose it won’t break
>> anything, but it might help with bugs like
>> <https://issues.guix.gnu.org/60002>.
>
> This wasn’t under my radar and I think it’s too late for such a change
> now.

OK.


> But look, we can do 1.4.1 next month if we want it.  There’s a position
> for a release management team (2–3 people) coming up BTW, so you can all
> prepare your applications.  :-)

I cannot guarantee being available or a good enough decision maker, but
I’m most grateful to you and all maintainers.

Regards,
Florian


  reply	other threads:[~2022-12-18 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:38 Release progress, week 10 Ludovic Courtès
2022-12-15 21:26 ` cirrus (was Re: Release progress, week 10) pelzflorian (Florian Pelz)
2022-12-17 19:18   ` pelzflorian (Florian Pelz)
2022-12-18 15:11   ` Ludovic Courtès
2022-12-18 16:27     ` pelzflorian (Florian Pelz) [this message]
2022-12-17 12:11 ` Release progress, week 10 zimoun
2022-12-18 15:13   ` Ludovic Courtès
2022-12-19 10:29     ` zimoun
2022-12-19 21:34       ` Ludovic Courtès

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=87bko0vfqv.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).