unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Theodoros Foradis <theodoros@foradis.org>
Cc: 27683-done@debbugs.gnu.org
Subject: bug#27683: [PATCH] gnu: libjaylink: Update to 699b700. openocd: Update to 0.10.0
Date: Thu, 28 Sep 2017 14:24:10 +0200	[thread overview]
Message-ID: <874lrnt3it.fsf@gnu.org> (raw)
In-Reply-To: <87wp4lgv3v.fsf@foradis.org> (Theodoros Foradis's message of "Tue, 26 Sep 2017 21:42:40 +0300")

Hi Theodoros,

Theodoros Foradis <theodoros@foradis.org> skribis:

>> Overall the changes look good to me, but can you clarify if they need to
>> be applied in the same commit like this?
>
> It has been some time since I submitted version 2 of the patch,
> splitting it in two.
>
> I revisited the patch and it wouldn't apply on master, so I reply with
> the rebased patch that applies on current master.

I went ahead and applied both.  Sorry that it took so long!

Thank you,
Ludo’.

      parent reply	other threads:[~2017-09-28 12:25 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
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     ` Ludovic Courtès [this message]

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=874lrnt3it.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27683-done@debbugs.gnu.org \
    --cc=theodoros@foradis.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).