From: "Junio C Hamano"
"Philip Oakley" writes:
One issue I notice a few weeks ago is that `git help --all` does not
list all of the available git help pages, rather it just limits
itself
to the available command pages.
This means that new users can't discover those additional help pages
in
"Philip Oakley" writes:
> One issue I notice a few weeks ago is that `git help --all` does not
> list all of the available git help pages, rather it just limits itself
> to the available command pages.
>
> This means that new users can't discover those additional help pages
> in any easy manner.
- Original Message -
From: "Jeff King"
To: "Junio C Hamano"
Cc: "Matthieu Moy" ;
Sent: Wednesday, August 08, 2012 9:54 PM
Subject: Re: [PATCH 2/4] check-docs: update non-command documentation
list
On Wed, Aug 08, 2012 at 12:24:29PM -0700, Junio C Ham
On Wed, Aug 08, 2012 at 12:24:29PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > The check-docs target looks at Documentation/git*txt and
> > complains if any entry does not have a matching command.
> > Therefore we need to explicitly ignore any entries which are
> > not meant to descri
Jeff King writes:
> The check-docs target looks at Documentation/git*txt and
> complains if any entry does not have a matching command.
> Therefore we need to explicitly ignore any entries which are
> not meant to describe a command (like gitattributes.txt).
> This list has grown stale over time,
The check-docs target looks at Documentation/git*txt and
complains if any entry does not have a matching command.
Therefore we need to explicitly ignore any entries which are
not meant to describe a command (like gitattributes.txt).
This list has grown stale over time, so let's bring it up to
date.
6 matches
Mail list logo
