From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New “ungrafting” branch
Date: Thu, 10 Dec 2020 18:13:29 -0500 [thread overview]
Message-ID: <87a6ul5k6e.fsf@gmail.com> (raw)
In-Reply-To: <87v9dcv8mt.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 08 Dec 2020 12:29:14 +0100")
Hello Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Guix!
>
> Following discussions on IRC, I’ve created a new ‘ungrafting’ branch
> that does nothing but ungraft things.
>
> The rationale is that grafts incur additional overhead when installing
> things (the time to create those grafts), so it’s good to clean them up
> once in a while. Ungrafting in a dedicated branch means we know the
> branch is “safe”, unlike more exploratory branches like ‘staging’ and
> ‘core-updates’.
>
> The plan is to start building it later today, and to hopefully be done
> in a week or so.
>
> Thoughts?
To me, staging is not enough exploratory the point to warrant an
additional ungrafting branch (my preference would be to rather see
staging merged sooner), but then I haven't kept a close look of what's
gone to it recently.
Having more branches also translates to more load on the CI, unless I'm
missing something.
Thank you for the initiative,
Maxim
next prev parent reply other threads:[~2020-12-10 23:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:29 New “ungrafting” branch Ludovic Courtès
2020-12-08 14:13 ` zimoun
2020-12-08 14:17 ` Andreas Enge
2020-12-08 18:20 ` Leo Famulari
2020-12-14 10:32 ` zimoun
2020-12-14 16:16 ` Leo Famulari
2020-12-14 20:03 ` Mark H Weaver
2020-12-14 21:00 ` Leo Famulari
2020-12-18 11:29 ` Andreas Enge
2020-12-18 2:33 ` zimoun
2020-12-08 19:02 ` Christopher Baines
2020-12-14 9:52 ` Ludovic Courtès
2020-12-10 23:13 ` Maxim Cournoyer [this message]
2021-01-15 5:57 ` Mark H Weaver
2021-01-15 21:02 ` Leo Famulari
2021-01-21 11:15 ` Ludovic Courtès
2021-01-21 21:33 ` Leo Famulari
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=87a6ul5k6e.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).