git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Max Horn <max@quendi.de>
Subject: Re: [PATCH] Rename {git- => git}remote-helpers.txt
Date: Thu, 31 Jan 2013 17:33:05 -0500	[thread overview]
Message-ID: <20130131223305.GB21729@sigill.intra.peff.net> (raw)
In-Reply-To: <3f26b82599aa2a45897d345c851fab4751c55810.1359669205.git.john@keeping.me.uk>

On Thu, Jan 31, 2013 at 09:59:50PM +0000, John Keeping wrote:

> 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".

Maybe it is just me, but the fact that accessing the manpage is now:

  man gitremote-helpers

feels weird to me. I know it technically follows our syntactic rules,
but having the lack of dash be significant between "git" and "remote",
but then having a dash later makes it hard on the eyes.

Would it make more sense to just call it "gitremotehelpers", and then
access it as:

  git help remotehelpers

or

  man gitremotehelpers

?

That has it its own ugliness (two words run together), but at least my
version of man will accept arbitrary capitalization, allowing:

  git help remoteHelpers

and

  man gitremoteHelpers

I dunno.

-Peff

  parent reply	other threads:[~2013-01-31 22:33 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   ` [PATCH] gitremote-helpers.txt: rename from git-remote-helpers.txt John Keeping
2013-01-31 20:18     ` 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 [this message]
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=20130131223305.GB21729@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    --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).