From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH 2/3] gnu: Update python-fixtures
Date: Fri, 09 Oct 2015 14:18:11 +0200
Message-ID: <87pp0os0ak.fsf@gnu.org>
References: <1442874675-31473-1-git-send-email-tipecaml@gmail.com>
	<1442874675-31473-3-git-send-email-tipecaml@gmail.com>
	<CAJ=RwfYwaN5n5du4ki9SDRHccrZRs-76pY3JCN2YrwGAKM=EPw@mail.gmail.com>
	<5601CC0B.3090601@gmail.com> <87io6vy5vb.fsf@gnu.org>
	<5616E2FD.6030801@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46275)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZkWct-0008OZ-1C
	for guix-devel@gnu.org; Fri, 09 Oct 2015 08:18:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1ZkWcn-0006MS-W6
	for guix-devel@gnu.org; Fri, 09 Oct 2015 08:18:18 -0400
In-Reply-To: <5616E2FD.6030801@gmail.com> (Cyril Roelandt's message of "Thu, 8
	Oct 2015 23:41:17 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 09/27/2015 10:17 PM, Ludovic Court=C3=A8s wrote:
>> Yeah, two commits would do IMO: one to add python-pbr-0.11, and the
>> other one for the rest.
>>=20
>> Could you do that?  This patch series needs to go in before it
>> accumulates dust.
>
> No, it'd be a bloody pain.
>
> If I just add python-pbr-0.11, then I'd have to change its inputs in the
> next patch (python-fixtures -> python-fixtures-0.3.16), so it adds weird
> stuff in the next commit.
>
> The thing is, this is a terrible mess, and the only way to have
> something easily understandable in the git history is to do this in one
> single, clean commit. I'm already having a hard time resisting the urge
> of writing a 3-paragraph commit log to explain everything ;)

Well OK, if that=E2=80=99s what it takes, let=E2=80=99s do it.

Thanks,
Ludo=E2=80=99.