From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: gnu: inetutils: Update to 2.4.
Date: Thu, 16 Mar 2023 13:43:48 -0700 [thread overview]
Message-ID: <CAFHYt55fZGHRvhrwG05YykLpLqmvUSm0vwyK+EPXUBREzRoJYQ@mail.gmail.com> (raw)
In-Reply-To: <87edpqlsza.fsf@gmail.com>
Hi Maxim,
On Tue, Mar 14, 2023 at 6:11 PM Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:
>
> Until everybody has a good grasp of the new process, I think sticking to
> the documented one may be best for now
The bug was retitled 'core-updates' per your request. [1]
I didn't mean to set a tone in the discussion and merely hoped to
embrace—by mistake it turns out—an existing consensus. My apologies!
May this action please invite further dialog, as needed.
Kind regards
Felix Lechner
[1] https://issues.guix.gnu.org/62154
next prev parent reply other threads:[~2023-03-16 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 1:26 gnu: inetutils: Update to 2.4 Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 15:52 ` Maxim Cournoyer
2023-03-14 16:37 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 19:49 ` Andreas Enge
2023-03-15 1:10 ` Maxim Cournoyer
2023-03-15 2:49 ` Leo Famulari
2023-03-15 3:30 ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Maxim Cournoyer
2023-03-15 11:37 ` Efraim Flashner
2023-03-15 13:32 ` Branch and release process Maxim Cournoyer
2023-03-15 13:37 ` Andreas Enge
2023-03-15 11:56 ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Leo Famulari
2023-03-15 12:04 ` Christopher Baines
2023-03-15 7:48 ` gnu: inetutils: Update to 2.4 Andreas Enge
2023-03-15 13:37 ` Maxim Cournoyer
2023-03-16 20:43 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-03-17 16:32 ` Maxim Cournoyer
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=CAFHYt55fZGHRvhrwG05YykLpLqmvUSm0vwyK+EPXUBREzRoJYQ@mail.gmail.com \
--to=guix-devel@gnu.org \
--cc=felix.lechner@lease-up.com \
--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.
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).