From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyril Roelandt Subject: Re: [PATCH 2/3] gnu: Update python-fixtures Date: Thu, 8 Oct 2015 23:41:17 +0200 Message-ID: <5616E2FD.6030801@gmail.com> References: <1442874675-31473-1-git-send-email-tipecaml@gmail.com> <1442874675-31473-3-git-send-email-tipecaml@gmail.com> <5601CC0B.3090601@gmail.com> <87io6vy5vb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkIwI-0007ik-O1 for guix-devel@gnu.org; Thu, 08 Oct 2015 17:41:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkIwE-0003N8-Bv for guix-devel@gnu.org; Thu, 08 Oct 2015 17:41:26 -0400 In-Reply-To: <87io6vy5vb.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: =?UTF-8?Q?Ludovic_Court=c3=a8s?= Cc: guix-devel On 09/27/2015 10:17 PM, Ludovic Courtès wrote: > Yeah, two commits would do IMO: one to add python-pbr-0.11, and the > other one for the rest. > > 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 ;) Cyril.