git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Keeping <john@keeping.me.uk>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Max Horn <max@quendi.de>,
	Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: [PATCH] gitremote-helpers.txt: rename from git-remote-helpers.txt
Date: Thu, 31 Jan 2013 20:08:14 +0000	[thread overview]
Message-ID: <fc96ae61bb64ce19e856d7a1624e2130c99afd47.1359662569.git.john@keeping.me.uk> (raw)
In-Reply-To: <7vfw1ijtz2.fsf@alter.siamese.dyndns.org>

When looking up a topic via "git help <topic>", git-help prepends "git-"
to topics that are the names of commands (either builtin or found on the
path) and "git" (no hyphen) to any other topic name.

"git-remote-helpers" is not the name of a command, so "git help
remote-helpers" looks for "gitremote-helpers" and does not find it.

Fix this by renaming "git-remote-helpers.txt" to
"gitremote-helpers.txt".

Signed-off-by: John Keeping <john@keeping.me.uk>
---
On Wed, Jan 30, 2013 at 12:28:49PM -0800, Junio C Hamano wrote:
> John Keeping <john@keeping.me.uk> writes:
> >
> > Does this mean that "git-remote-helpers.txt" should lose the first
> > hyphen or is help.c not being clever enough in some way?
> 
> I think it is the former.  "git help tutorial" works exactly the
> same way.

This is the patch to rename it to "gitremote-helpers.txt".

Would we want to do something to avoid breaking links to the existing
document as well?

 Documentation/git-remote-testgit.txt                            | 2 +-
 Documentation/{git-remote-helpers.txt => gitremote-helpers.txt} | 6 +++---
 Documentation/urls.txt                                          | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)
 rename Documentation/{git-remote-helpers.txt => gitremote-helpers.txt} (99%)

diff --git a/Documentation/git-remote-testgit.txt b/Documentation/git-remote-testgit.txt
index 612a625..f791d73 100644
--- a/Documentation/git-remote-testgit.txt
+++ b/Documentation/git-remote-testgit.txt
@@ -23,7 +23,7 @@ The best way to learn more is to read the comments and source code in
 
 SEE ALSO
 --------
-linkgit:git-remote-helpers[1]
+linkgit:gitremote-helpers[1]
 
 GIT
 ---
diff --git a/Documentation/git-remote-helpers.txt b/Documentation/gitremote-helpers.txt
similarity index 99%
rename from Documentation/git-remote-helpers.txt
rename to Documentation/gitremote-helpers.txt
index e36fdcb..0c91aba 100644
--- a/Documentation/git-remote-helpers.txt
+++ b/Documentation/gitremote-helpers.txt
@@ -1,9 +1,9 @@
-git-remote-helpers(1)
-=====================
+gitremote-helpers(1)
+====================
 
 NAME
 ----
-git-remote-helpers - Helper programs to interact with remote repositories
+gitremote-helpers - Helper programs to interact with remote repositories
 
 SYNOPSIS
 --------
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 539c0a0..3ca122f 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -55,7 +55,7 @@ may be used:
 
 where <address> may be a path, a server and path, or an arbitrary
 URL-like string recognized by the specific remote helper being
-invoked. See linkgit:git-remote-helpers[1] for details.
+invoked. See linkgit:gitremote-helpers[1] for details.
 
 If there are a large number of similarly-named remote repositories and
 you want to use a different format for them (such that the URLs you
-- 
1.8.1.1

  reply	other threads:[~2013-01-31 20:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 20:11 git-remote-helpers.txt: should it be gitremote-helpers.txt? John Keeping
2013-01-30 20:28 ` Junio C Hamano
2013-01-31 20:08   ` John Keeping [this message]
2013-01-31 20:18     ` [PATCH] gitremote-helpers.txt: rename from git-remote-helpers.txt Matthieu Moy
2013-01-31 20:36       ` Junio C Hamano
2013-01-31 21:59         ` [PATCH] Rename {git- => git}remote-helpers.txt John Keeping
2013-01-31 22:13           ` Junio C Hamano
2013-01-31 22:28             ` John Keeping
2013-01-31 22:43               ` Junio C Hamano
2013-01-31 22:56                 ` John Keeping
2013-01-31 23:49                   ` Junio C Hamano
2013-01-31 22:33           ` Jeff King
2013-01-31 22:48             ` Junio C Hamano
2013-01-31 23:04             ` Jonathan Nieder
2013-01-31 23:11               ` Junio C Hamano
2013-01-31 23:13                 ` Jonathan Nieder
2013-02-01  5:03               ` Jeff King
2013-02-01  5:37                 ` Junio C Hamano
2013-02-01  7:33                   ` Jeff King
2013-02-01  8:25                     ` Jeff King
2013-02-01  8:26                       ` [PATCH 1/2] Documentation/Makefile: clean up MAN*_TXT lists Jeff King
2013-02-01 19:20                         ` Jonathan Nieder
2013-02-01 19:38                           ` Junio C Hamano
2013-02-01 19:38                           ` Jeff King
2013-02-01 19:41                             ` Jeff King
2013-02-01  8:27                       ` [PATCH 2/2] docs: convert "concept" manpages to git-* Jeff King
2013-02-01 19:25                         ` Jonathan Nieder
2013-02-01 18:52                     ` [PATCH] Rename {git- => git}remote-helpers.txt Junio C Hamano
2013-02-01 19:00                       ` Jeff King
2013-02-01 22:15                         ` Junio C Hamano
2013-01-31 22:28     ` [PATCH] gitremote-helpers.txt: rename from git-remote-helpers.txt Tomas Carnecky
2013-01-31 22:45       ` 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=fc96ae61bb64ce19e856d7a1624e2130c99afd47.1359662569.git.john@keeping.me.uk \
    --to=john@keeping.me.uk \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=max@quendi.de \
    /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 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 NNTP newsgroup(s).