From: Philip Oakley <philipoakley@iee.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Duy Nguyen <pclouds@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v3 2/2] Doc: git.txt: remove backticks from link and add git-scm.com/docs
Date: Thu, 16 May 2019 12:25:47 +0100 [thread overview]
Message-ID: <d79d5e70-ec3a-c6ca-b23d-a44edf2579d2@iee.org> (raw)
In-Reply-To: <xmqqbm035fhx.fsf@gitster-ct.c.googlers.com>
On 16/05/2019 02:56, Junio C Hamano wrote:
> Philip Oakley <philipoakley@iee.org> writes:
>
>> 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.
> Good. I just ran
>
> $ git grep '`https*://' Documentation/
>
> to see if any hits I see are for the real URL the user may want to
> click on. There are some that are pointing at real sites, but I do
> not think users would want to clickon many of them while reading the
> documentation.
I'd had a quick brows and mainly found example.com ;-) Any other excepts
were at the other end of the doc relative to git(1)...
>
> Except perhaps for these to see what's there:
>
> Documentation/git-archimport.txt: Attempt to auto-register archives at `http://mirrors.sourcecontrol.net`
That domain is gone. Whole line should probably be removed.
> Documentation/git-cvsimport.txt:* cvs2git (part of cvs2svn), `http://subversion.apache.org/`
>
Still there. Still updated - last news 2019-04-24. Could remove backticks.
Philip
next prev parent reply other threads:[~2019-05-16 11:25 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 ` [PATCH v3 2/2] Doc: git.txt: remove backticks from link and add git-scm.com/docs Philip Oakley
2019-05-16 1:56 ` Junio C Hamano
2019-05-16 11:25 ` Philip Oakley [this message]
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=d79d5e70-ec3a-c6ca-b23d-a44edf2579d2@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.