From: Brice Waegeneire <brice@waegenei.re>
To: 53308@debbugs.gnu.org
Subject: [bug#53308] [PATCH 0/3] deluge: update to 2.0.5
Date: Sun, 16 Jan 2022 22:35:47 +0100 [thread overview]
Message-ID: <20220116213547.5128-1-brice@waegenei.re> (raw)
In addition to updating deluge and the using the new style this add an
explanation requested by Leo in <https://issues.guix.gnu.org/52486#7>.
Brice Waegeneire (3):
gnu: deluge: Update to 2.0.5.
gnu: deluge: Adjust style.
gnu: deluge: Add explanation about wrap phase.
gnu/packages/bittorrent.scm | 49 ++++++++++++++++++-------------------
1 file changed, 24 insertions(+), 25 deletions(-)
base-commit: 27914cb4b72142e2cc99172996c83709e9491437
--
2.34.0
next reply other threads:[~2022-01-16 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 21:35 Brice Waegeneire [this message]
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 ` bug#53308: [PATCH 0/3] deluge: update to 2.0.5 Brice Waegeneire
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=20220116213547.5128-1-brice@waegenei.re \
--to=brice@waegenei.re \
--cc=53308@debbugs.gnu.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).