unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add re2.
Date: Fri, 19 Aug 2016 13:33:15 +0100	[thread overview]
Message-ID: <87shu1x7jo.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20160818204310.GD2393@jasmine>

Leo Famulari <leo@famulari.name> writes:

> When moving packages around, all users of the package need to have their
> module imports updated. Copyright attribution must be carefully handled.
> And merging the various *-updates branches into master and vice versa
> becomes more complicated and prone to error.

Perhaps it makes sense to schedule package moves just after big merges
(e.g. before cutting a new core-updates branch). Or have them in
separate short-lived branches to give users (and Hydra, considering the
recent tcsh evaluation failure) some time to test and prepare.

My 2 NOK,
Marius

  parent reply	other threads:[~2016-08-19 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 13:05 [PATCH] gnu: Add re2 Marius Bakke
2016-08-16 17:59 ` Leo Famulari
2016-08-17 10:34   ` Marius Bakke
2016-08-17 15:18     ` Marius Bakke
2016-08-18 20:43       ` Leo Famulari
2016-08-19  7:35         ` Alex Kost
2016-08-19 22:49           ` Leo Famulari
2016-08-19 11:37         ` Marius Bakke
2016-08-19 12:33         ` Marius Bakke [this message]
2016-09-12 13:38       ` Alex Kost
2016-09-12 14:09         ` Marius Bakke
2016-09-13  7:44           ` Alex Kost
2016-08-18 20:37     ` 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=87shu1x7jo.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).