From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Fix counting problem in `format-patch -<n>`
Date: Sat, 28 Aug 2010 01:58:14 +0530 [thread overview]
Message-ID: <1282940896-18350-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
Here's a patch avoid the 'git format-patch -3' confusion I complained
about earlier along with a test. 1/2 isn't strictly a prerequisite,
but results seem to be unpredictable without it.
Based on master.
Ramkumar Ramachandra (2):
t4014-format-patch: Call test_tick before committing
format-patch: Don't go over merge commits
Documentation/git-format-patch.txt | 2 +-
builtin/log.c | 7 +------
t/t4014-format-patch.sh | 21 +++++++++++++++++++++
3 files changed, 23 insertions(+), 7 deletions(-)
--
1.7.2.2.409.gdbb11.dirty
next reply other threads:[~2010-08-27 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 20:28 Ramkumar Ramachandra [this message]
2010-08-27 20:28 ` [PATCH 1/2] t4014-format-patch: Call test_tick before committing Ramkumar Ramachandra
2010-08-27 20:28 ` [PATCH 2/2] format-patch: Don't go over merge commits 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=1282940896-18350-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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).