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

Re: [PATCH 7/7] git-shortlog.txt: make SYNOPSIS match log, update OPTIONS

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 21, 2013, 19:06 UTC
Message-ID
<7vip3fsnxw.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1366534252-12099-8-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 12 quoted lines
> diff --git a/Documentation/git-shortlog.txt b/Documentation/git-shortlog.txt
> index c7f7f51..2a66518 100644
> --- a/Documentation/git-shortlog.txt
> +++ b/Documentation/git-shortlog.txt
> @@ -8,8 +8,8 @@ git-shortlog - Summarize 'git log' output
>  SYNOPSIS
>  --------
>  [verse]
> -git log --pretty=short | 'git shortlog' [-h] [-n] [-s] [-e] [-w]
> -'git shortlog' [-n|--numbered] [-s|--summary] [-e|--email] [-w[<width>[,<indent1>[,<indent2>]]]] <commit>...
> +git log --pretty=short | 'git shortlog' [<options>]
> +'git shortlog' [<options>] [<revision range>] [[\--] <path>...]

You will need to update what you added in [PATCH 2/7] to builtin/shortlog.c to match this in this patch.

Show 14 quoted lines
>  DESCRIPTION
>  -----------
> @@ -56,6 +56,23 @@ OPTIONS
>  If width is `0` (zero) then indent the lines of the output without wrapping
>  them.
>  
> +<revision range>::
> +	Consider only commits in the specified revision range.  When no
> +	<revision range> is specified, it defaults to 'HEAD' (ie. the
> +	whole history leading to the current commit).  master..next
> +	specifies all the commits reachable from 'next, but not from
> +	'master'. For a complete list of ways to spell
> +	<revision range>, see the "Specifying Ranges" section of
> +	linkgit:gitrevisions[7].
Match the text you modified in 'log.txt' in [PATCH 5/7], perhaps?
Show 5 quoted lines
> +[\--] <path>...::
> +	Consider only commits that are enough to explain how the files
> +	that match the specified paths came to be.  See "History
> +	Simplification" below for details and other simplification
> +	modes.

Have you read the resulting "git shortlog --help"? Do we even have "below"?

Show 6 quoted lines
> ++
> +Paths may need to be prefixed with "\-- " to separate them from
> +options or the revision range, when confusion arises.
>  
>  MAPPING AUTHORS
>  ---------------
Previous: Ramkumar Ramachandra
Message 10 of 10 in “Documentation/shortlog improvements”
  1. 0/7 Documentation/shortlog improvementsRamkumar Ramachandra, Apr 21, 2013
  2. 1/7 git-shortlog.txt: remove (-h|--help) from OPTIONSRamkumar Ramachandra, Apr 21, 2013
  3. 2/7 builtin/shortlog.c: make usage string consistent with logRamkumar Ramachandra, Apr 21, 2013
  4. 3/7 revisions.txt: clarify the .. and ... syntaxRamkumar Ramachandra, Apr 21, 2013
  5. 4/7 git-log.txt: order OPTIONS properly; move <since>..<until>Ramkumar Ramachandra, Apr 21, 2013
  6. 5/7 git-log.txt: generalize <since>..<until>Ramkumar Ramachandra, Apr 21, 2013
  7. Junio C HamanoApr 21, 2013
  8. 6/7 git-log.txt: rewrite note on why "--" may be requiredRamkumar Ramachandra, Apr 21, 2013
  9. 7/7 git-shortlog.txt: make SYNOPSIS match log, update OPTIONSRamkumar Ramachandra, Apr 21, 2013
  10. Junio C HamanoApr 21, 2013

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.