diff options
| author | Felix Lechner <felix.lechner@lease-up.com> | 2023-05-18 10:50:55 -0700 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2023-05-24 15:04:00 +0200 |
| commit | 3c2f833257a35df4ba96c92326270c0983af0946 (patch) | |
| tree | 5e8f2b681aef8d95c90bfb3cfa907bb4010b856f /doc/contributing.texi | |
| parent | e54d574add30acd4603a7a2e5cd60dd634ba4e12 (diff) | |
| download | guix-3c2f833257a35df4ba96c92326270c0983af0946.tar guix-3c2f833257a35df4ba96c92326270c0983af0946.tar.gz | |
doc: contributing.texi: Specify recipient via equal sign in 'git send-email --to'.
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'.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Diffstat (limited to 'doc/contributing.texi')
| -rw-r--r-- | doc/contributing.texi | 6 |
1 files 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 |