From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jacob Keller <jacob.keller@gmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
Andreas Schwab <schwab@linux-m68k.org>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: man page for "git remote set-url" seems confusing/contradictory
Date: Wed, 18 Apr 2018 16:56:35 -0400 [thread overview]
Message-ID: <20180418205635.GU29831@zaya.teonanacatl.net> (raw)
In-Reply-To: <xmqqd0yxl6n9.fsf@gitster-ct.c.googlers.com>
Junio C Hamano wrote:
> Jacob Keller <jacob.keller@gmail.com> writes:
>
>> Maybe something like:
>>
>> "Note that the push URL and the fetch URL, even though they can be set
>> differently, are expected to refer to the same repository. For
>> example, the fetch URL might use an unauthenticated transport, while
>> the push URL generally requires authentication" Then follow this bit
>> with the mention of multiple remotes.
>>
>> (I think "repository" conveys the meaning better than "place".
>> Technically, the URLs can be completely different as long as they end
>> up contacting the same real server repository.)
>
> Sounds sensible. Let's see if there is any further input and then
> somebody pleaes wrap this up in a final patch ;-)
A pointer to the "GIT URLS" section in git-fetch(1) might
also be useful? That section is provided via urls.txt and
urls-remotes.txt and is included the git-clone, git-fetch,
git-pull, and git-push man pages.
We could also include urls-remotes.txt in git-remote, though
that seems like a lot of text to add to yet another man
page. Maybe a giturls.txt could be created and referenced
(as a further enhancement if someone is inclined).
Tangentially (and I don't know if it's worth fixing), while
poking around the documentation which includes urls.txt I
noticed that git-clone.txt refers readers to the "URLS
section below" when the name of the section is "GIT URLS".
I doubt any readers would be confused, but it would be
consistent with the other files which include urls.txt to
use "GIT URLS" as the referenced section name.
-- >& --
Subject: [PATCH] doc/clone: update caption for GIT URLS cross-reference
The description of the <repository> argument directs readers to "See the
URLS section below". When generating HTML this becomes a link to the
"GIT URLS" section. When reading the man page in a terminal, the
caption is slightly misleading. Use "GIT URLS" as the caption to avoid
an confusion.
The man page produced by asciidoc doesn't include hyperlinks. The
description of the <repository> argument simply
Signed-off-by: Todd Zullinger <tmz@pobox.com>
---
Documentation/git-clone.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 42ca7b5095..b844b9957c 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -260,7 +260,7 @@ or `--mirror` is given)
<repository>::
The (possibly remote) repository to clone from. See the
- <<URLS,URLS>> section below for more information on specifying
+ <<URLS,GIT URLS>> section below for more information on specifying
repositories.
<directory>::
--
2.17.0
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The ultimate result of shielding men from the effects of folly is to
fill the world with fools.
-- Herbert Spencer
next prev parent reply other threads:[~2018-04-18 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 12:43 man page for "git remote set-url" seems confusing/contradictory Robert P. J. Day
2018-04-16 16:14 ` Andreas Schwab
2018-04-16 16:19 ` Robert P. J. Day
2018-04-16 18:20 ` Jacob Keller
2018-04-16 23:13 ` Junio C Hamano
2018-04-17 1:01 ` Jacob Keller
2018-04-17 15:34 ` Robert P. J. Day
2018-04-17 17:41 ` Jacob Keller
2018-04-18 0:06 ` Junio C Hamano
2018-04-18 20:56 ` Todd Zullinger [this message]
2018-04-19 4:17 ` Martin Ågren
2018-04-19 17:32 ` [PATCH] doc/clone: update caption for GIT URLS cross-reference Todd Zullinger
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180418205635.GU29831@zaya.teonanacatl.net \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=rpjday@crashcourse.ca \
--cc=schwab@linux-m68k.org \
/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://80x24.org/mirrors/git.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).