From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: 63575@debbugs.gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: [bug#63575] [PATCH 1/2] doc: contributing.texi: Specify recipient via equal sign in 'git send-email --to'.
Date: Thu, 18 May 2023 10:50:55 -0700 [thread overview]
Message-ID: <febb4fe6e43d2eb969ddc6550421a33fe3552154.1684432045.git.felix.lechner@lease-up.com> (raw)
In-Reply-To: <cover.1684432045.git.felix.lechner@lease-up.com>
The documentation for git send-email recommends the use of an equal sign when
specifying a recipient with the --to option. [1] Adjusts the reference manual
accordingly.
[1] https://git-scm.com/docs/git-send-email
* doc (contributing.texi): Specify recipient via equal sign in
'git send-email --to'.
---
doc/contributing.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 7bf350ee0d..f692872c04 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1529,7 +1529,7 @@ the patchset.
@example
$ git send-email -@var{NUMBER_COMMITS} -v@var{REVISION} \
- --to @var{ISSUE_NUMBER}@@debbugs.gnu.org
+ --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org
@end example
If need be, you may use @option{--cover-letter --annotate} to send
@@ -1561,7 +1561,7 @@ You can run the following command to have the @code{Mentors} team put in
CC of a patch series:
@example
-$ git send-email --to @var{ISSUE_NUMBER}@@debbugs.gnu.org \
+$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org \
--header-cmd='etc/teams.scm cc-mentors-header-cmd' *.patch
@end example
@@ -1571,7 +1571,7 @@ current Git repository to review, you can run:
@example
$ guix shell -D guix
-[env]$ git send-email --to @var{ISSUE_NUMBER}@@debbugs.gnu.org -2
+[env]$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org -2
@end example
@node Tracking Bugs and Patches
--
2.40.1
next prev parent reply other threads:[~2023-05-18 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 17:48 [bug#63575] [PATCH 0/2] Fix typos in documentation Felix Lechner via Guix-patches via
2023-05-18 17:50 ` Felix Lechner via Guix-patches via [this message]
2023-05-18 17:50 ` [bug#63575] [PATCH 2/2] doc: guix.texi: Add Texinfo line breaks Felix Lechner via Guix-patches via
2023-05-24 12:04 ` bug#63575: [PATCH 0/2] Fix typos in documentation Ludovic Courtès
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=febb4fe6e43d2eb969ddc6550421a33fe3552154.1684432045.git.felix.lechner@lease-up.com \
--to=guix-patches@gnu.org \
--cc=63575@debbugs.gnu.org \
--cc=felix.lechner@lease-up.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).