All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
	Philippe Blain <levraiphilippeblain@gmail.com>
Subject: [PATCH v2] git.txt: fix typos in 'linkgit' macro invocation
Date: Tue, 22 Dec 2020 15:44:42 +0000	[thread overview]
Message-ID: <pull.934.v2.git.git.1608651882510.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.934.git.git.1608651140403.gitgitgadget@gmail.com>

From: Philippe Blain <levraiphilippeblain@gmail.com>

The 'linkgit' Asciidoc macro is misspelled as 'linkit' in the
description of 'GIT_SEQUENCE_EDITOR' since the addition of that variable
to git(1) in 902a126eca (doc: mention GIT_SEQUENCE_EDITOR and
'sequence.editor' more, 2020-08-31). Also, it uses two colons instead of
one.

Fix that.

Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
---
    git.txt: fix typos in 'linkgit' macro invocation
    
    Changes since v1:
    
     * also fixed the fact that I had used two colons instead of one.
    
    Sorry for not checking the doc build before sending v1.

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-934%2Fphil-blain%2Ffix-linkgit-git1-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-934/phil-blain/fix-linkgit-git1-v2
Pull-Request: https://github.com/git/git/pull/934

Range-diff vs v1:

 1:  978e328fb94 ! 1:  494173a5865 git.txt: fix typos in 'linkgit' macro invocation
     @@ Commit message
          The 'linkgit' Asciidoc macro is misspelled as 'linkit' in the
          description of 'GIT_SEQUENCE_EDITOR' since the addition of that variable
          to git(1) in 902a126eca (doc: mention GIT_SEQUENCE_EDITOR and
     -    'sequence.editor' more, 2020-08-31).
     +    'sequence.editor' more, 2020-08-31). Also, it uses two colons instead of
     +    one.
      
          Fix that.
      
     @@ Documentation/git.txt: other
       	when editing the todo list of an interactive rebase. See also
      -	linkit::git-rebase[1] and the `sequence.editor` option in
      -	linkit::git-config[1].
     -+	linkgit::git-rebase[1] and the `sequence.editor` option in
     -+	linkgit::git-config[1].
     ++	linkgit:git-rebase[1] and the `sequence.editor` option in
     ++	linkgit:git-config[1].
       
       `GIT_SSH`::
       `GIT_SSH_COMMAND`::


 Documentation/git.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git.txt b/Documentation/git.txt
index c463b937a86..a6d4ad0818b 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -609,8 +609,8 @@ other
 `GIT_SEQUENCE_EDITOR`::
 	This environment variable overrides the configured Git editor
 	when editing the todo list of an interactive rebase. See also
-	linkit::git-rebase[1] and the `sequence.editor` option in
-	linkit::git-config[1].
+	linkgit:git-rebase[1] and the `sequence.editor` option in
+	linkgit:git-config[1].
 
 `GIT_SSH`::
 `GIT_SSH_COMMAND`::

base-commit: 6d3ef5b467eccd2769f1aa1c555d317d3c8dc707
-- 
gitgitgadget

  reply	other threads:[~2020-12-22 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 15:32 [PATCH] git.txt: fix typos in 'linkgit' macro invocation Philippe Blain via GitGitGadget
2020-12-22 15:44 ` Philippe Blain via GitGitGadget [this message]
2020-12-22 20:05   ` [PATCH v2] " Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.934.v2.git.git.1608651882510.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=levraiphilippeblain@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.