[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pcmanfm version update
From: |
Ludovic Courtès |
Subject: |
Re: pcmanfm version update |
Date: |
Wed, 13 Apr 2016 23:31:02 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Leo Famulari <address@hidden> skribis:
> On Sat, Apr 09, 2016 at 10:59:03PM +0300, Efraim Flashner wrote:
>> We do have some packages that have to be updated together, acme and
>> letsencrypt, python-cryptography and python-cryptography-vectors. But
>> those do have a commit message that they are updated together.
>
> If those packages were updated separately, the build would break after
> the first commit. Neither of those package pairs works if the versions
> are not in sync [0].
>
> In my opinion, that is a valid reason for updating multiple packages in
> the same commit.
If that is the case (I wouldn’t be surprised), I agree it’s a valid
reason.
Anyway, it’s no big deal, so we shouldn’t block otherwise
uncontroversial and non-disrupting patches for 1 week just because of
this IMO.
Thoughts? Someone applies it? :-)
Ludo’.
- mplayer version update, rain1, 2016/04/04
- Re: mplayer version update, Mark H Weaver, 2016/04/04
- pcmanfm version update, rain1, 2016/04/07
- Re: pcmanfm version update, Alex Kost, 2016/04/09
- Message not available
- Re: pcmanfm version update, Alex Kost, 2016/04/09
- Re: pcmanfm version update, Andreas Enge, 2016/04/09
- Re: pcmanfm version update, Efraim Flashner, 2016/04/09
- Re: pcmanfm version update, Mathieu Lirzin, 2016/04/09
- Re: pcmanfm version update, Leo Famulari, 2016/04/09
- Re: pcmanfm version update,
Ludovic Courtès <=
- Re: pcmanfm version update, Leo Famulari, 2016/04/13