From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 60374-done@debbugs.gnu.org
Subject: bug#60374: [PATCH] gnu: gpodder: Update to 3.11.0.
Date: Thu, 05 Jan 2023 23:04:31 +0100 [thread overview]
Message-ID: <87lemg1vv4.fsf@gnu.org> (raw)
In-Reply-To: <20221228031717.24390-1-raingloom@riseup.net> (raingloom@riseup.net's message of "Wed, 28 Dec 2022 04:17:17 +0100")
raingloom <raingloom@riseup.net> skribis:
> * gnu/packages/gpodder.scm (gpodder): Update to 3.11.0.
Applied, thanks!
prev parent reply other threads:[~2023-01-05 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 3:17 [bug#60374] [PATCH] gnu: gpodder: Update to 3.11.0 raingloom
2023-01-05 22:04 ` 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=87lemg1vv4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60374-done@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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).