From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Thomas Rast <trast@student.ethz.ch>,
Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 0/2] log/ format-patch improvements
Date: Wed, 25 Aug 2010 14:14:21 +0530 [thread overview]
Message-ID: <20100825084416.GC3280@kytes> (raw)
In-Reply-To: <1282422531-29673-1-git-send-email-artagnon@gmail.com>
Hi,
Ramkumar Ramachandra writes:
> The first patch implements Jakub's suggestion. Arguably, it's slightly
> complicated- it took me more than a few minutes to do the math with
> `nr` and `nr_i`.
>
> The second patch clarifies the meaning of the `-<n>` option. We should
> also probably force the mutual exclusivity of `-<n>` and <revision
> range> to avoid confusion.
>
> Additionally, thanks to Thomas for drilling into me the fundamental
> difference between -<n> and a revision range (on IRC).
>
> Ramkumar Ramachandra (2):
> git-format-patch: Print a diagnostic message when ignoring commits
> log: Improve description of '-<n>' option in documentation
>
> Documentation/git-format-patch.txt | 2 +-
> Documentation/git-log.txt | 2 +-
> builtin/log.c | 42 ++++++++++++++++++++++++++---------
> 3 files changed, 33 insertions(+), 13 deletions(-)
Do you see value in this patch or is it just unnecessary baggage?
-- Ram
next prev parent reply other threads:[~2010-08-25 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 20:28 [PATCH 0/2] log/ format-patch improvements Ramkumar Ramachandra
2010-08-21 20:28 ` [PATCH 1/2] git-format-patch: Print a diagnostic message when ignoring commits Ramkumar Ramachandra
2010-08-21 20:28 ` [PATCH 2/2] log: Improve description of '-<n>' option in documentation Ramkumar Ramachandra
2010-08-25 8:44 ` Ramkumar Ramachandra [this message]
2010-08-25 20:54 ` [PATCH 0/2] log/ format-patch improvements Jonathan Nieder
2010-08-26 5:34 ` Ramkumar Ramachandra
2010-08-26 5:46 ` Jonathan Nieder
2010-08-26 7:06 ` Thomas Rast
2010-08-26 15:37 ` Junio C Hamano
2010-08-26 17:52 ` Ramkumar Ramachandra
2010-08-25 22:09 ` 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=20100825084416.GC3280@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.