From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel@gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: gnu: inetutils: Update to 2.4.
Date: Tue, 14 Mar 2023 11:52:56 -0400 [thread overview]
Message-ID: <87lejzmisn.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt54Wen1m38WJ4W07cYAtwx294BiWY7y0CwC_Y9FNC4Wu9A@mail.gmail.com> (Felix Lechner via's message of "Sun, 12 Mar 2023 18:26:17 -0700")
Hi Felix,
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> writes:
> Hi,
>
> With core-updates possibly being replaced by feature branches, I am
> not sure where to place this update to GNU Inetutils 2.4.
>
> The patch series [1] will rebuild 3,416 packages.
In the future, try to remember using the --subject-prefix='PATCH
core-updates', to avoid committers mistakenly pushing this to master, as
hinted in the manual: info '(guix) Sending a Patch Series' :-).
Thanks for the heads-up!
--
Maxim
next prev parent reply other threads:[~2023-03-14 15:53 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 [this message]
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.
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=87lejzmisn.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=felix.lechner@lease-up.com \
--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).