git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Pieter de Bie <pdebie@ai.rug.nl>, git@vger.kernel.org
Subject: Re: [PATCH] git-help: Try to find html pages without the git- prefix
Date: Tue, 29 Apr 2008 07:18:47 +0200	[thread overview]
Message-ID: <200804290718.47961.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vy76x8e0s.fsf@gitster.siamese.dyndns.org>

Le mardi 29 avril 2008, Junio C Hamano a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> > We already have the following files following that scheme:
> >
> > gitk.txt
> > gitattributes.txt
> > gitignore.txt
> > gitcli.txt
> > gitmodules.txt
> > git.txt
> >
> > And for example the following commands are already working:
> >
> > $ git help -w gitmodules
> > $ git help -m gitmodules
> > $ man gitmodules
>
> That is not surprise as gitattributes(5), gitignore(5) and gitmodules(5)
> work by design.  They are valid manual pages in section 5 (file formats).
>
> I am not sure about hooks let alone gitcli --- they are not something you
> would traditionally place in section 5.

Aren't there other man sections where we could put them ?

> It would be nice if "git help <any path you see in Documentation/>"
> worked as expected, 

I agree and that means that we should find an appropriate man section for 
everything in "Documentation/". Otherwise how could "git help -m <any path 
you see in Documentation/>" work ?

Thanks,
Christian.

> although I personally tend to go to the *.txt files 
> ;-)

      reply	other threads:[~2008-04-29  5:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 10:13 [PATCH] git-help: Try to find html pages without the git- prefix Pieter de Bie
2008-04-29  3:13 ` Christian Couder
2008-04-29  4:45   ` Junio C Hamano
2008-04-29  5:18     ` Christian Couder [this message]

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=200804290718.47961.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pdebie@ai.rug.nl \
    /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).