Thanks so much for your answer! indeed, I assumed that "git
apply" *applies* the patch, and thus I didn't read its manual page.
And indeed I now saw that
git apply --summary patchFile
git apply --summary --numstat patchFile
give this info
On Sun, May 8, 2016 at 6:40 AM, Dale R. Worley <wor...@alum.mit.edu> wrote:
> Konstantin Khomoutov <flatw...@users.sourceforge.net> writes:
>> On Fri, 6 May 2016 18:56:01 +0300
>> Kevin Wilson <wkev...@gmail.com> wrote:
>>> Suppose you have a patch named 0001-great_change.patch
>>> Is there a way by which, using some git command, you can find out
>>> which files this patch changes, without that
>>> you will edit (or cat/more ) that 0001-great_change.patch file?
>> Have you tried to read the manual page of the `git apply` command?
>> It's all there.
> I wouldn't know for a fact, but I suspect that Keven assumed that "git
> apply" *applies* the patch, and thus didn't read its manual page, since
> it is clearly not relevant to his problem. So it's probably better to
> There are certain options to "git apply" which, despite the name of
> the function, do not apply the patch but rather display information
> about the patch, and some of those options list the files that the
> patch affects.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.