From: Philip Oakley <philipoakley@iee.org>
To: Git List <git@vger.kernel.org>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Duy Nguyen <pclouds@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: [PATCH v3 2/2] Doc: git.txt: remove backticks from link and add git-scm.com/docs
Date: Wed, 15 May 2019 23:47:09 +0100 [thread overview]
Message-ID: <20190515224709.2936-3-philipoakley@iee.org> (raw)
In-Reply-To: <20190515224709.2936-1-philipoakley@iee.org>
While checking the html formatted git(1) manual page, it was noted
that the link to https://git.github.io/htmldocs/git.html was formatted
as code. Remove the backticks.
While at it, add the https://git-scm.com/docs link which one reviewer
noted had linkable section headings.
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
Documentation/git.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index dbf92f6ac6..edcb9936b5 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -33,7 +33,8 @@ individual Git commands with "git help command". linkgit:gitcli[7]
manual page gives you an overview of the command-line command syntax.
A formatted and hyperlinked copy of the latest Git documentation
-can be viewed at `https://git.github.io/htmldocs/git.html`.
+can be viewed at https://git.github.io/htmldocs/git.html
+or https://git-scm.com/docs.
OPTIONS
--
2.21.0.windows.1.1517.gbad5f960a3.dirty
next prev parent reply other threads:[~2019-05-15 22:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 20:47 git --help not actually showing the git(1) help page Philip Oakley
2019-05-13 20:53 ` Jeff King
2019-05-13 21:55 ` Philip Oakley
2019-05-13 22:44 ` Junio C Hamano
2019-05-14 14:05 ` Philip Oakley
2019-05-14 15:24 ` [PATCH] git.c: show usage for accessing " Philip Oakley
2019-05-15 0:17 ` Emily Shaffer
2019-05-15 1:53 ` Jeff King
2019-05-15 6:43 ` Philip Oakley
2019-05-15 8:11 ` [PATCH v2] " Philip Oakley
2019-05-15 8:14 ` Eric Sunshine
2019-05-15 22:47 ` [PATCH v3 0/2] " Philip Oakley
2019-05-15 22:47 ` [PATCH v3 1/2] git.c: show usage for " Philip Oakley
2019-05-15 22:47 ` Philip Oakley [this message]
2019-05-16 1:56 ` [PATCH v3 2/2] Doc: git.txt: remove backticks from link and add git-scm.com/docs Junio C Hamano
2019-05-16 11:25 ` Philip Oakley
2019-05-16 22:22 ` Jeff King
2019-05-16 23:09 ` Philip Oakley
2019-05-15 6:36 ` [PATCH] git.c: show usage for accessing the git(1) help page Philip Oakley
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=20190515224709.2936-3-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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.