From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 61978-done@debbugs.gnu.org
Subject: bug#61978: [PATCH] gnu: src: Update to 1.31.
Date: Mon, 06 Mar 2023 16:21:00 +0800 [thread overview]
Message-ID: <87v8jep9xv.fsf@envs.net> (raw)
In-Reply-To: <20230305130946.39016-1-paul@apatience.com> (Paul A. Patience's message of "Sun, 05 Mar 2023 13:09:54 +0000")
"Paul A. Patience" <paul@apatience.com> writes:
> * gnu/packages/version-control.scm (src): Update to 1.31.
Pushed, thank you!
prev parent reply other threads:[~2023-03-06 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:09 [bug#61978] [PATCH] gnu: src: Update to 1.31 Paul A. Patience
2023-03-06 8:21 ` 宋文武 via Guix-patches via [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=87v8jep9xv.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=61978-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=paul@apatience.com \
/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).