From: Brice Waegeneire <brice@waegenei.re>
To: Leo Famulari <leo@famulari.name>
Cc: 53308-done@debbugs.gnu.org
Subject: bug#53308: [PATCH 0/3] deluge: update to 2.0.5
Date: Mon, 17 Jan 2022 22:54:01 +0100 [thread overview]
Message-ID: <878rvet4ee.fsf_-_@waegenei.re> (raw)
In-Reply-To: <YeXKCVgIj1aFAvNa@jasmine.lan> (Leo Famulari's message of "Mon, 17 Jan 2022 14:56:57 -0500")
Leo Famulari <leo@famulari.name> writes:
[...]
> Thanks, these patches LGTM!
Thank you for the review, pushed as 31577d879dd6e9d78e21b842953a804e0bc3fe92.
prev parent reply other threads:[~2022-01-17 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 21:35 [bug#53308] [PATCH 0/3] deluge: update to 2.0.5 Brice Waegeneire
2022-01-17 19:34 ` [bug#53308] [PATCH] deluge: update to 2.0.5 (patchs attached) brice
2022-01-17 19:56 ` Leo Famulari
2022-01-17 21:54 ` Brice Waegeneire [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rvet4ee.fsf_-_@waegenei.re \
--to=brice@waegenei.re \
--cc=53308-done@debbugs.gnu.org \
--cc=leo@famulari.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.