From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
info-guix@gnu.org, help-guix <help-guix@gnu.org>
Subject: Re: GNU Guix maintainer rotation
Date: Fri, 07 Jan 2022 09:21:14 -0600 [thread overview]
Message-ID: <8735lzvafp.fsf@gmail.com> (raw)
In-Reply-To: <87pmp4r4v8.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 06 Jan 2022 15:22:51 -0500")
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> I'd like to bring your attention to a change to the current Guix
> maintainers collective; in a nutshell, Ludovic and Marius are stepping
> down from maintainer-ship while Efraim is joining.
Thank you very much for your guidance, support, and hard work, Ludovic and Marius. Likewise, Efraim, thank you for your contributions, and for stepping up!
--
Katherine
next prev parent reply other threads:[~2022-01-07 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 20:22 GNU Guix maintainer rotation Maxim Cournoyer
2022-01-06 21:22 ` Jérémy Korwin-Zmijowski
2022-01-07 15:21 ` Katherine Cox-Buday [this message]
2022-01-08 1:09 ` Leo Famulari
2022-01-08 11:48 ` Oliver Propst
2022-01-08 13:43 ` Edouard Klein
2022-01-09 16:43 ` Todor Kondić
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=8735lzvafp.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=info-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).