[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/3] gnu: Update python-fixtures
From: |
Cyril Roelandt |
Subject: |
Re: [PATCH 2/3] gnu: Update python-fixtures |
Date: |
Thu, 8 Oct 2015 23:41:17 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.2.0 |
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.
- Re: [PATCH 2/3] gnu: Update python-fixtures,
Cyril Roelandt <=