From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New “ungrafting” branch
Date: Tue, 08 Dec 2020 19:02:47 +0000 [thread overview]
Message-ID: <87ft4gi0iw.fsf@cbaines.net> (raw)
In-Reply-To: <87v9dcv8mt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> 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?
Sounds good. I'm not quite sure what you mean by safe though, it's
definitely likely that things will behave the same, but it's not
certain. Additionally, I guess there will be cases were things fail to
build when the replacement is used in the build process.
I thought the process used to be to push the update to
staging/core-updates when the replacement was introduced to master?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-12-08 19:29 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 [this message]
2020-12-14 9:52 ` Ludovic Courtès
2020-12-10 23:13 ` Maxim Cournoyer
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=87ft4gi0iw.fsf@cbaines.net \
--to=mail@cbaines.net \
--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).