From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: gnu: inetutils: Update to 2.4.
Date: Tue, 14 Mar 2023 21:10:33 -0400 [thread overview]
Message-ID: <87edpqlsza.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt55otH2BOk9QAeuNo=-64v1Dg_p7rnmBk7ZvR5mMgRLu7A@mail.gmail.com> (Felix Lechner's message of "Tue, 14 Mar 2023 09:37:23 -0700")
Hi Felix,
Felix Lechner <felix.lechner@lease-up.com> writes:
> Hi Maxim,
>
> On Tue, Mar 14, 2023 at 8:53 AM Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
>>
>> In the future, try to remember using the --subject-prefix='PATCH
>> core-updates', to avoid committers mistakenly pushing this to master
>
> Thank you for your response! I wrote for guidance on that issue. I am
> sorry that was unclear from my message.
>
> With the core-updates process now abandoned, I retitled the issue to
Could you share the reference of that? I'm not against it, but our
currently documented process still mention the good old staging and
core-updates branches.
> "[PATCH wip-inetutils 0/4] gnu: inetutils: Update to 2.4".
>
> Does that work for you?
>
> I am happy to retitle as "core-updates" as you suggested, if that's
> what you want. Of course, you can also retitle it in any way you think
> is best.
Until everybody has a good grasp of the new process, I think sticking to
the documented one may be best for now, as it makes it clear that this
cause a mass rebuild and shouldn't land to master.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-15 1:11 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 [this message]
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=87edpqlsza.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).