git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolaj Shurkaev <snnicky@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: git log -z doesn't separate commits with NULs
Date: Thu, 23 Feb 2012 16:48:43 +0300	[thread overview]
Message-ID: <4F4643BB.8090001@gmail.com> (raw)
In-Reply-To: <m34nuhelnf.fsf@localhost.localdomain>

For example there are commits that affect not only files in folder A but 
files in folder B, C and so on.
If I do format-patch that will give me nice patches, but there are 
modifications of folders B, C and so on there.
I do not know a way to generate patches via format-patch that affect 
only files in folder A.

This is why I wrote those scripts.

23.02.2012 16:15, Jakub Narebski пишет:
> Nikolaj Shurkaev<snnicky@gmail.com>  writes:
>
>> Thank you very much for your tips. They really helped me. I was trying
>> to create patches that would affect only some given files or
>> folders. By this moment I have the following:
>>
>> GeneratePatches.sh
>> ---------------------
>> #!/bin/bash
>> #parameter 1 -<since>..<to>
>> #parameter 2 - path to file
>> git log -z --reverse --format=email --patch "$1" -- "$2" | xargs
>> --null --max-args=1 ./CreatePatchFile.sh
>> ---------------------
>>
>> and CreatePatchFile.sh
>> ---------------------
>> #!/bin/bash
>>
>> myPatchNumber=$(ls ./*-patch.patch 2>/dev/null | wc -l)
>> let "myPatchNumber += 1"
>>
>> patchFile="./"$(printf "%04d" $myPatchNumber)"-patch.patch"
>> echo "$@">  "$patchFile"
>> ---------------------
>>
>> I call
>> ./GeneratePatches.sh HEAD~3..HEAD SomePath
>> and that produces something very similar to what I want.
>>
>> Perhaps there is a better way to do that.
> So what git-format-patch is lacking?
>

  reply	other threads:[~2012-02-23 13:49 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 [this message]
2012-02-23 19:34         ` Jeff King
2012-02-23 20:07           ` Junio C Hamano
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=4F4643BB.8090001@gmail.com \
    --to=snnicky@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=peff@peff.net \
    /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).