Jeff King writes:
> On Fri, Feb 01, 2013 at 10:52:52AM -0800, Junio C Hamano wrote:
>
>> > 4. Replace the rename "gitfoo" above with a "see git-foo..." pointer.
>> > Users of "git help foo" would not ever see this, but people who
>> > have trained their fingers to type "man gitfoo" wo
On Fri, Feb 01, 2013 at 10:52:52AM -0800, Junio C Hamano wrote:
> > 4. Replace the rename "gitfoo" above with a "see git-foo..." pointer.
> > Users of "git help foo" would not ever see this, but people who
> > have trained their fingers to type "man gitfoo" would, along with
> > a
Jeff King writes:
> Right. So we have some that must be "gitfoo", and others that do not
> care. If we turned "githooks" into "git-hooks" and removed the "is it a
> command?" magic from "git help", then "git help hooks" would still find
> hooks. And likewise, "git help gitignore" would still find
On Fri, Feb 01, 2013 at 02:33:52AM -0500, Jeff King wrote:
> I am starting to think it has grown in an unnecessarily complex
> direction, and we would be much happier just calling all of the
> "concept" documentation "git-".
>
> The steps I see are:
I am still undecided on whether it is a good i
On Thu, Jan 31, 2013 at 09:37:51PM -0800, Junio C Hamano wrote:
> Jeff King writes:
>
> > What was the original rationale for the "gitfoo" form? Was it just to
> > visually distinguish command manpages from non-command manpages? I can't
> > remember the origins now.
>
> b27a23e (Documentation:
Jeff King writes:
> What was the original rationale for the "gitfoo" form? Was it just to
> visually distinguish command manpages from non-command manpages? I can't
> remember the origins now.
b27a23e (Documentation: convert tutorials to man pages, 2008-05-24)
turns "tutorial.txt" into "gittutor
On Thu, Jan 31, 2013 at 03:04:55PM -0800, Jonathan Nieder wrote:
> Jeff King wrote:
>
> > 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 d
John Keeping writes:
> On Thu, Jan 31, 2013 at 02:43:20PM -0800, Junio C Hamano wrote:
>> John Keeping writes:
>>
>> > Yes. Should I change it to "git-remote-helpers.html.in" and then copy
>> > it into place? That seems like the simplest answer and means that
>> > "*.html" will continue to re
Junio C Hamano wrote:
> Jonathan Nieder writes:
>> Yes. I have thought for years that it should be git-remote-helpers,
>> that "git help" should be tweaked to look for that, and that the
>> existing gitrepository-layout and friends should be replaced with
>> redirects.
>
> Because of the "git he
Jonathan Nieder writes:
> Jeff King wrote:
>
>> 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",
Jeff King wrote:
> 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 make
On Thu, Jan 31, 2013 at 02:43:20PM -0800, Junio C Hamano wrote:
> John Keeping writes:
>
> > Yes. Should I change it to "git-remote-helpers.html.in" and then copy
> > it into place? That seems like the simplest answer and means that
> > "*.html" will continue to refer only to generated files.
>
Jeff King writes:
> Maybe it is just me, but the fact that accessing the manpage is now:
>
> man gitremote-helpers
>
> feels weird to me.
It feels equally weird to say "man gitremotehelpers" (or in general
"man git-thing" or "man gitconcept"), to me. I gave up and switched
to "git help remote
John Keeping writes:
> Yes. Should I change it to "git-remote-helpers.html.in" and then copy
> it into place? That seems like the simplest answer and means that
> "*.html" will continue to refer only to generated files.
I'd like to see if we can have a way to keep its look as the default
css g
On Thu, Jan 31, 2013 at 09:59:50PM +, John Keeping wrote:
> When looking up a topic via "git help ", 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 n
On Thu, Jan 31, 2013 at 02:13:10PM -0800, Junio C Hamano wrote:
> John Keeping writes:
>
> > When looking up a topic via "git help ", 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.
> >
John Keeping writes:
> When looking up a topic via "git help ", 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-h
When looking up a topic via "git help ", 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-helpe
18 matches
Mail list logo
