unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Theodoros Foradis <theodoros.for@openmailbox.org>, 27683@debbugs.gnu.org
Subject: [bug#27683] [PATCH] gnu: libjaylink: Update to 699b700. openocd:	Update to 0.10.0
Date: Tue, 25 Jul 2017 22:52:53 +0200	[thread overview]
Message-ID: <87fudkjl22.fsf@fastmail.com> (raw)
In-Reply-To: <871sp4a56d.fsf@openmailbox.org>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

Theodoros Foradis <theodoros.for@openmailbox.org> 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 ;-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-07-25 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  9:59 [bug#27683] [PATCH] gnu: libjaylink: Update to 699b700. openocd: Update to 0.10.0 Theodoros Foradis
2017-07-23  0:12 ` Leo Famulari
2017-07-25 15:48   ` Theodoros Foradis
2017-07-25 20:52     ` Marius Bakke [this message]
2017-07-29 18:31       ` [bug#27683] [PATCH v2 1/2] gnu: libjaylink: Update to commit 699b700 Theodoros Foradis
2017-07-29 18:31         ` [bug#27683] [PATCH v2 2/2] gnu: openocd: Update to 0.10.0 Theodoros Foradis
2017-09-26 18:42   ` [bug#27683] [PATCH] gnu: libjaylink: Update to 699b700. " Theodoros Foradis
2017-09-26 18:46     ` [bug#27683] [PATCH v3 1/2] gnu: libjaylink: Update to commit 699b700 Theodoros Foradis
2017-09-26 18:46       ` [bug#27683] [PATCH v3 2/2] gnu: openocd: Update to 0.10.0 Theodoros Foradis
2017-09-28 12:24     ` bug#27683: [PATCH] gnu: libjaylink: Update to 699b700. " Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fudkjl22.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=27683@debbugs.gnu.org \
    --cc=theodoros.for@openmailbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).