git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/7] Documentation/shortlog improvements
Date: Sun, 21 Apr 2013 14:20:45 +0530	[thread overview]
Message-ID: <1366534252-12099-1-git-send-email-artagnon@gmail.com> (raw)

In this round, I've incorporated suggestions made by Junio:

[3/7] is entirely new.

[4/7] and [5/7] together re-order and replace '<since>..<until>' with
'<revision range>', in contrast to a single patch which attempted to
fix '<since>..<until>' in-place in the previous version.

[6/7] uses "the revision range" instad of "revisions".

[7/7] copies the latest text from git-log.txt, and doesn't attempt to
add rev-list-options.txt.

There's a parallel discussion going on about fixing the meaning of
"revision", but this series is entirely unrelated to that.

Ramkumar Ramachandra (7):
  git-shortlog.txt: remove (-h|--help) from OPTIONS
  builtin/shortlog.c: make usage string consistent with log
  revisions.txt: clarify the .. and ... syntax
  git-log.txt: order OPTIONS properly; move <since>..<until>
  git-log.txt: generalize <since>..<until>
  git-log.txt: rewrite note on why "--" may be required
  git-shortlog.txt: make SYNOPSIS match log, update OPTIONS

 Documentation/git-log.txt      | 22 ++++++++++++----------
 Documentation/git-shortlog.txt | 25 +++++++++++++++++++------
 Documentation/revisions.txt    |  6 ++++--
 builtin/shortlog.c             |  4 +---
 4 files changed, 36 insertions(+), 21 deletions(-)

-- 
1.8.2.1.501.gd2949c7

             reply	other threads:[~2013-04-21  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21  8:50 Ramkumar Ramachandra [this message]
2013-04-21  8:50 ` [PATCH 1/7] git-shortlog.txt: remove (-h|--help) from OPTIONS Ramkumar Ramachandra
2013-04-21  8:50 ` [PATCH 2/7] builtin/shortlog.c: make usage string consistent with log Ramkumar Ramachandra
2013-04-21  8:50 ` [PATCH 3/7] revisions.txt: clarify the .. and ... syntax Ramkumar Ramachandra
2013-04-21  8:50 ` [PATCH 4/7] git-log.txt: order OPTIONS properly; move <since>..<until> Ramkumar Ramachandra
2013-04-21  8:50 ` [PATCH 5/7] git-log.txt: generalize <since>..<until> Ramkumar Ramachandra
2013-04-21 18:54   ` Junio C Hamano
2013-04-21  8:50 ` [PATCH 6/7] git-log.txt: rewrite note on why "--" may be required Ramkumar Ramachandra
2013-04-21  8:50 ` [PATCH 7/7] git-shortlog.txt: make SYNOPSIS match log, update OPTIONS Ramkumar Ramachandra
2013-04-21 19:06   ` Junio C Hamano

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=1366534252-12099-1-git-send-email-artagnon@gmail.com \
    --to=artagnon@gmail.com \
    --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).