From: Nikolaj Shurkaev Date: Fri, 24 Feb 2012 09:21:13 GMT Subject: Re: git log -z doesn't separate commits with NULs Message-ID: <4F475689.4040203@gmail.com> In-Reply-To: <7vy5rt2u0c.fsf@alter.siamese.dyndns.org> Hello. Thank you for the hint. git format-patch HEAD~3..HEAD -- SomePath does exactly what I need. But that way of usage is not described in git documentation thus I thought there is no way to do that. I've just double checked git format-patch --help doesn't describe that. I'll propose to put something like this into git documentation -------------------------------------------------------------------------------------------- diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index 6ea9be7..63267c6 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -23,6 +23,7 @@ SYNOPSIS [--cover-letter] [--quiet] [] [ | ] + [[\--] ...] DESCRIPTION ----------- @@ -219,6 +220,12 @@ you can use `--suffix=-patch` to get `0001-description-of-my-change-patch`. range are always formatted as creation patches, independently of this flag. +[\--] ...:: + Put in patches only those modifications that affect specified files + and folders. It's important to understand that log message of the + commit may become inappropriate because some parts of patch may be + cut off. + CONFIGURATION ------------- You can specify extra mail header lines to be added to each message, -------------------------------------------------------------------------------------------- -- Nikolaj. 23.02.2012 23:07, Junio C Hamano пишет: > Jeff King 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"). >