From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nikolaj Shurkaev <snnicky@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: git log -z doesn't separate commits with NULs
Date: Thu, 23 Feb 2012 12:07:47 -0800 [thread overview]
Message-ID: <7vy5rt2u0c.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120223193451.GB30132@sigill.intra.peff.net> (Jeff King's message of "Thu, 23 Feb 2012 14:34:51 -0500")
Jeff King <peff@peff.net> writes:
> On Thu, Feb 23, 2012 at 04:48:43PM +0300, Nikolaj Shurkaev wrote:
>
> Doesn't:
>
> git format-patch HEAD~3..HEAD SomePath
>
> do what you want? It is certainly designed to, and it seems to work for
> me.
It is not quite "designed to", though.
It happens to work that way, and I do not think we want to forbid its use,
but we would want to discourage anybody from blindly using it without
thinking if the end results suits his/her purpose (and the reason should
be obvious to those who think, the hint is "log message").
next prev parent reply other threads:[~2012-02-23 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 9:14 git log -z doesn't separate commits with NULs Nikolaj Shurkaev
2012-02-23 10:02 ` Luke Diamand
2012-02-23 10:27 ` Jeff King
2012-02-23 10:17 ` Johannes Sixt
2012-02-23 12:11 ` Nikolaj Shurkaev
2012-02-23 10:24 ` Jeff King
2012-02-23 12:17 ` Nikolaj Shurkaev
2012-02-23 13:15 ` Jakub Narebski
2012-02-23 13:48 ` Nikolaj Shurkaev
2012-02-23 19:34 ` Jeff King
2012-02-23 20:07 ` Junio C Hamano [this message]
2012-02-24 9:21 ` Nikolaj Shurkaev
2012-02-24 9:52 ` Jeff King
2012-02-24 20:03 ` Junio C Hamano
2012-02-24 20:46 ` Jeff King
2012-02-24 21:14 ` Junio C Hamano
2012-02-24 21:16 ` Jeff King
2012-03-03 13:41 ` Nikolaj Shurkaev
2012-02-24 22:11 ` Jakub Narebski
2012-02-24 22:27 ` Junio C Hamano
2012-02-23 10:35 ` Andreas Schwab
2012-02-23 12:19 ` Nikolaj Shurkaev
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=7vy5rt2u0c.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=snnicky@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).