From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 0/7] Documentation/shortlog improvements
Date: Mon, 22 Apr 2013 11:00:24 +0530 [thread overview]
Message-ID: <1366608631-21734-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
The re-roll was necessary due to minor/silly mistakes in v2, as
pointed out by Junio.
The builtin/shortlog.c patch has moved to the end until we change
'<since>..<until>' to '<revision range>' everywhere else. We use
'<revision range>' here too.
[4/7] has been replaced with the version Junio fixed up and put in
`pu`.
[6/7] has been updated to copy sections from log.txt properly, and
omit the "see below for History Simplification" part.
Thanks.
Ramkumar Ramachandra (7):
git-shortlog.txt: remove (-h|--help) from OPTIONS
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
builtin/shortlog.c: make usage string consistent with log
Documentation/git-log.txt | 22 ++++++++++++----------
Documentation/git-shortlog.txt | 23 +++++++++++++++++------
Documentation/revisions.txt | 6 ++++--
builtin/shortlog.c | 4 +---
4 files changed, 34 insertions(+), 21 deletions(-)
--
1.8.2.1.501.gd2949c7
next reply other threads:[~2013-04-22 5:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 5:30 Ramkumar Ramachandra [this message]
2013-04-22 5:30 ` [PATCH 1/7] git-shortlog.txt: remove (-h|--help) from OPTIONS Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 2/7] revisions.txt: clarify the .. and ... syntax Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 3/7] git-log.txt: order OPTIONS properly; move <since>..<until> Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 4/7] git-log.txt: generalize <since>..<until> Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 5/7] git-log.txt: rewrite note on why "--" may be required Ramkumar Ramachandra
2013-04-25 0:02 ` Re* " Junio C Hamano
2013-04-25 5:17 ` Ramkumar Ramachandra
2013-04-29 16:33 ` Junio C Hamano
2013-04-29 17:38 ` Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 6/7] git-shortlog.txt: make SYNOPSIS match log, update OPTIONS Ramkumar Ramachandra
2013-04-22 5:30 ` [PATCH 7/7] builtin/shortlog.c: make usage string consistent with log Ramkumar Ramachandra
2013-04-22 7:20 ` [PATCH 6.5/7] builtin/log.c: make usage string consistent with doc Ramkumar Ramachandra
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=1366608631-21734-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).