From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/3] Expat and libxslt changes for core-updates
Date: Fri, 10 Jun 2016 20:49:27 -0400 [thread overview]
Message-ID: <20160611004927.GA1242@jasmine> (raw)
In-Reply-To: <87bn3919oa.fsf@gnu.org>
On Fri, Jun 10, 2016 at 02:59:49PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> > The merge will probably be messy...
>
> We should leave it to you, to minimize breakage.
Okay, should I do it today or is core-updates frozen?
> > Off-topic: A regular package and a grafted package on master, and an
> > updated version of the package on core-updates... this is getting very
> > complicated and we should try our best to avoid such tangled situations
> > in the future.
>
> Do you think it would help to delay such upgrades in ‘core-updates’
> until the time where ‘core-updates’ is getting ready for merge?
I don't know if there is a great solution; I think this is a really
perverse case.
I think of core-updates as the place to put these sorts of changes. If
we were to decide to delay the changes, we'd all have our own private
core-updates forks, and then we'd probably duplicate work and forget
about things. What do you think?
If anybody else feels burdened by this as I do, your ideas are very
welcome :)
next prev parent reply other threads:[~2016-06-11 0:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 0:54 [PATCH 0/3] Expat and libxslt changes for core-updates Leo Famulari
2016-06-08 0:54 ` [PATCH 1/3] gnu: expat: Fix CVE-2016-0718 Leo Famulari
2016-06-08 13:25 ` Ludovic Courtès
2016-06-09 16:20 ` Leo Famulari
2016-06-08 0:54 ` [PATCH 2/3] gnu: Remove unused patch Leo Famulari
2016-06-08 13:25 ` Ludovic Courtès
2016-06-08 0:54 ` [PATCH 3/3] gnu: libxslt: Update to 1.1.29 Leo Famulari
2016-06-08 13:26 ` Ludovic Courtès
2016-06-08 10:10 ` [PATCH 0/3] Expat and libxslt changes for core-updates Efraim Flashner
2016-06-08 11:50 ` Leo Famulari
2016-06-08 11:55 ` Leo Famulari
2016-06-08 13:27 ` Ludovic Courtès
2016-06-09 16:26 ` Leo Famulari
2016-06-09 16:43 ` Leo Famulari
2016-06-09 23:19 ` Leo Famulari
2016-06-10 12:59 ` Ludovic Courtès
2016-06-11 0:49 ` Leo Famulari [this message]
2016-06-12 20:26 ` Ludovic Courtès
2016-06-13 2:20 ` Leo Famulari
2016-06-13 15:05 ` Ludovic Courtès
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=20160611004927.GA1242@jasmine \
--to=leo@famulari.name \
--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).