From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New “ungrafting” branch
Date: Fri, 15 Jan 2021 16:02:44 -0500 [thread overview]
Message-ID: <YAIC9P37Yqyd09l8@jasmine.lan> (raw)
In-Reply-To: <874kji4u86.fsf@netris.org>
On Fri, Jan 15, 2021 at 12:57:50AM -0500, Mark H Weaver wrote:
> 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.
>
> This is a good initiative, but it seems to have stalled. Is there a
> reason that it has not yet been merged into 'master'?
The ungrafting branch was merged into the staging branch. Unfortunately,
the staging branch is moving very slowly. I perceive a lack of
interest in working on it :/
I think that the ungrafting branch should have been kept separate and
merged into master quickly.
next prev parent reply other threads:[~2021-01-15 21:03 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
2021-01-15 5:57 ` Mark H Weaver
2021-01-15 21:02 ` Leo Famulari [this message]
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=YAIC9P37Yqyd09l8@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).