[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#27683] [PATCH] gnu: libjaylink: Update to 699b700. openocd: Update
From: |
Marius Bakke |
Subject: |
[bug#27683] [PATCH] gnu: libjaylink: Update to 699b700. openocd: Update to 0.10.0 |
Date: |
Tue, 25 Jul 2017 22:52:53 +0200 |
User-agent: |
Notmuch/0.24.2 (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu) |
Theodoros Foradis <address@hidden> writes:
> Hello Leo,
>
>> Overall the changes look good to me, but can you clarify if they need to
>> be applied in the same commit like this?
>
> I remember reading somewhere (irc or mailing list probably), that a
> package should not break between commits (to be able to bisect). That
> would be the case with openocd, if libjaylink is updated before openocd.
>
> If this concern is not valid, I can split the commit in two and resubmit
> the patches.
There are certain cases where updating together make a lot of sense,
such as the gstreamer- or qt-family packages. But for mostly-unrelated
programs it's better to have the patches in bite-sized chunks.
I agree that they should be updated separately. We often break packages
in commits, wittingly or not ;-)
signature.asc
Description: PGP signature