unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Attila Lendvai <attila@lendvai.name>
Cc: 52207-done@debbugs.gnu.org
Subject: bug#52207: [PATCH 1/2] gnu: python-daemon: Update to 2.3.0.
Date: Wed, 01 Dec 2021 18:40:25 +0100	[thread overview]
Message-ID: <8735ncxlyu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20211201154707.7865-1-attila@lendvai.name> (Attila Lendvai's message of "Wed, 1 Dec 2021 16:47:07 +0100")

Hello,

Attila Lendvai <attila@lendvai.name> writes:

> as requested, resending the patchset in only two commits (rationale:
> the packages are inter-dependent, and splitting the commit means that
> the commits would leave the repo in a broken state; thinking of
> git bisect, etc).

I applied the patches, thank you.

I tweaked the last one because it was based on a previous patch, not the
current state of the repository. I also fixed commit messages. You may
want to look at them.

Regards,
-- 
Nicolas Goaziou




      parent reply	other threads:[~2021-12-01 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 20:37 [bug#52207] [PATCH 1/5] gnu: python-daemon: Update to 2.3.0 Attila Lendvai
2021-11-30 20:44 ` [bug#52207] [PATCH 2/5] gnu: python-trezor-agent: Update to 0.14.4 Attila Lendvai
2021-11-30 20:44   ` [bug#52207] [PATCH 3/5] gnu: python-mnemonic: Update to 0.20 Attila Lendvai
2021-11-30 20:44   ` [bug#52207] [PATCH 4/5] gnu: python-trezor: Update to 0.12.4 Attila Lendvai
2021-11-30 20:44   ` [bug#52207] [PATCH 5/5] gnu: trezor-agent: Update to 0.11.0-1, aka git tag v0.14.4 Attila Lendvai
2021-12-01 15:47 ` [bug#52207] [PATCH 1/2] gnu: python-daemon: Update to 2.3.0 Attila Lendvai
2021-12-01 15:47   ` [bug#52207] [PATCH 2/2] gnu: Update Trezor support Attila Lendvai
2021-12-01 17:40   ` Nicolas Goaziou [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=8735ncxlyu.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=52207-done@debbugs.gnu.org \
    --cc=attila@lendvai.name \
    /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).