git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>, git@vger.kernel.org
Subject: Re: [PATCH 2/4] check-docs: update non-command documentation list
Date: Wed, 8 Aug 2012 16:54:56 -0400	[thread overview]
Message-ID: <20120808205456.GB29528@sigill.intra.peff.net> (raw)
In-Reply-To: <7vwr19rxua.fsf@alter.siamese.dyndns.org>

On Wed, Aug 08, 2012 at 12:24:29PM -0700, Junio C Hamano wrote:

> Jeff King <peff@peff.net> 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, so let's bring it up to
> > date.
> >
> > Signed-off-by: Jeff King <peff@peff.net>
> > ---
> > I really wonder if we would do better to match git-*.txt, since most of
> > the ignores are gitfoo(7) types of pages. We'd probably want to add back
> > in "git", "gitweb" and "gitk" explicitly, but they are already handled
> > specially above and below.
> 
> Quite possibly, yes.

Actually, my "already handled specially" is not quite accurate. That
special list is "things that are commands but are not necessarily
mentioned in the Makefile variables". But this list is "things that are
documented but do not begin with git-". The two should mostly be the
same, but the whole point of this exercise is to make sure they _are_
the same.

A better solution is to simply ask the Documentation directory what the
commands are, since it already knows (in the form of MAN1_TXT).

> Also "git gitk gitweb" may want to be made into a Makefile variable
> to be shared in the "above" and "below" (I do not know what to call
> them offhand---they are programs with special build rules that are
> not covered by ALL/SCRIPT_LIB/BUILTIN).

I couldn't think of a special name, either, but I think it is sufficient
to just create a new ALL_COMMANDS variable that includes those other
things, and then add to it.

> By the way, do we have a documentation for git-gui?  Perhaps it may
> want to be added to that "git gitk gitweb" list as a reminder that
> it lacks documentation.  One of the goals of the person who runs
> "make check-docs" should be to reduce the special case that appears
> at the beginning of that case statement.

Yes, it should be checked (and git-citool, too).

> I also wonder why "help" is not treated as a built-in?  Perhaps we
> should throw it in to "git gitk gitweb" list?  After all, it is a
> command that is available in "git foo" form, is documented, and is
> listed in the command-list.txt file.

Historically it was part of git.c, but these days it is a built-in and
does not need any special treatment from check-docs.

Patches for all to follow (on top of my previous 4).

  [5/4]: check-docs: factor out command-list
  [6/4]: check-docs: list git-gui as a command
  [7/4]: check-docs: drop git-help special-case
  [8/4]: check-docs: get documented command list from Makefile

-Peff

  reply	other threads:[~2012-08-08 20:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  7:58 [PATCH] Documentation: list git-credential in plumbing commands Matthieu Moy
2012-08-08 16:58 ` Junio C Hamano
2012-08-08 17:13   ` [PATCH v2] " Matthieu Moy
2012-08-08 18:31   ` [PATCH 0/4] update "make check-docs" Jeff King
2012-08-08 18:32     ` [PATCH 1/4] check-docs: mention gitweb specially Jeff King
2012-08-08 18:34     ` [PATCH 2/4] check-docs: update non-command documentation list Jeff King
2012-08-08 19:24       ` Junio C Hamano
2012-08-08 20:54         ` Jeff King [this message]
2012-08-08 20:56           ` [PATCH 5/4] check-docs: factor out command-list Jeff King
2012-08-08 20:56           ` [PATCH 6/4] check-docs: list git-gui as a command Jeff King
2012-08-08 20:57           ` [PATCH 7/4] check-docs: drop git-help special-case Jeff King
2012-08-08 20:57           ` [PATCH 8/4] check-docs: get documented command list from Makefile Jeff King
2012-08-08 21:35             ` Junio C Hamano
2012-08-08 22:11           ` [PATCH 2/4] check-docs: update non-command documentation list Philip Oakley
2012-08-08 22:51             ` Junio C Hamano
2012-08-09  6:34               ` Philip Oakley
2012-08-08 18:34     ` [PATCH 3/4] command-list: add git-sh-i18n Jeff King
2012-08-08 18:34     ` [PATCH 4/4] command-list: mention git-credential-* helpers Jeff King
2012-08-09  8:02       ` Matthieu Moy
2012-08-08 19:13     ` [PATCH 0/4] update "make check-docs" Junio C Hamano
2012-08-08 20:10       ` Jeff King

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=20120808205456.GB29528@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Matthieu.Moy@imag.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).