From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: is core-updates still a thing?
Date: Tue, 26 Sep 2023 12:28:35 -0400 [thread overview]
Message-ID: <8734z0291o.fsf@gmail.com> (raw)
In-Reply-To: <31817bba-f3b0-f4fb-e1b6-97955216232f@gmail.com> (Katherine Cox-Buday's message of "Tue, 26 Sep 2023 09:20:04 -0600")
Hi Katherine,
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
> On 9/24/23 1:27 AM, Andy Tai wrote:
>> Hi, curious if core-updates still a thing? There seems a branch by
>> that name and the manual still says patches causing large number of
>> rebuilds should go to core-updates, at least for these not aiming at a
>> specific feature branch.
> I have the same question.
>
> My understanding is that feature-branches are now the canonical way to
> work on things, and core-updates has become just another kind of
> feature-branch for landing groups of large changes that don't really
> fit anywhere; the difference being that it's now more ephemeral and
> "as needed" instead of the default for large changes.
>
> Do I have that right?
>
> I guess we need to update the manual?
I think that's right! Clarifications to the manual would be welcome.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-09-26 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 7:27 is core-updates still a thing? Andy Tai
2023-09-26 15:20 ` Katherine Cox-Buday
2023-09-26 16:28 ` Maxim Cournoyer [this message]
2023-09-27 9:54 ` Simon Tournier
2023-09-26 16:27 ` 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=8734z0291o.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=atai@atai.org \
--cc=cox.katherine.e@gmail.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).