Kevin Wilson writes:
> Dale,
> 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
For a non-gi
Dale,
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
Thanks again!
Kevin
On Sun, May 8, 2016 at 6:40 AM
Konstantin Khomoutov writes:
> On Fri, 6 May 2016 18:56:01 +0300
> Kevin Wilson 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
- Original Message -
From: "Kevin Wilson"
Hi,
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?
Regards,
K
On Fri, 6 May 2016 18:56:01 +0300
Kevin Wilson 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?
H
Hi,
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?
Regards,
Kevin
--
You received this message because you are s
