git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Improve and fix git-check-attr(1)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 14, 2008, 23:58 UTC
Message-ID
<7vabd6686n.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20081013175705.GA9538@diku.dk>
Jonas Fonseca <fonseca@diku.dk> writes:
Show 13 quoted lines
> Always use 'verse' for multi-line synopsis sections. Add output and
> example sections to document what output can be expected.
>
> Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
>
> ---
>  Documentation/git-check-attr.txt |   63 +++++++++++++++++++++++++++++++++++++-
>  1 files changed, 62 insertions(+), 1 deletions(-)
>
>  At least the first chunk should be applied. The last is a quick attempt
>  at documenting the expected output formally and with examples.
> ...
> tg: (340fcf4..) jf/man-git-check-attr (depends on: next)

Should this really have to depend on next? I have a feeling that a large part of this (sans --stdin/-z) is a 'maint' material.

Could you split this into two patches, one for 'maint' to describe the output format, and another for 'next' (or 'dp/checkattr') to update the SYNOPSIS part?

Previous: Jonas FonsecaNext: Jonas Fonseca
Message 2 of 4 in “Improve and fix git-check-attr(1)”
  1. Improve and fix git-check-attr(1)Jonas Fonseca, Oct 13, 2008
  2. Junio C HamanoOct 14, 2008
  3. 1/2 git-check-attr(1): add output and example sectionsJonas Fonseca, Oct 15, 2008
  4. 2/2 git-check-attr(1): use 'verse' for multi-line synopsis sectionsJonas Fonseca, Oct 15, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.