Re: git apply vs. renamed files index mismatch
From: Scott Wood <hidden>
Date: 2016-06-15 22:45:20
Also in:
linuxppc-dev
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: git apply vs. renamed files index mismatch · Junio C Hamano <hidden>
- 2016-06-15 · Re: git apply vs. renamed files index mismatch · Junio C Hamano <hidden>
- 2016-06-15 · Re: git apply vs. renamed files index mismatch · Anton Vorontsov <hidden>
- 2016-06-15 · Re: git apply vs. renamed files index mismatch · Junio C Hamano <hidden>
- 2016-06-15 · Re: git apply vs. renamed files index mismatch · Anton Vorontsov <hidden>
Anton Vorontsov wrote:
I always thought that posting "-M" patches to the public lists is discouraged since it is quite difficult to apply them via patch(1). Also think of non-git users...
I think the substantially enhanced reviewability trumps non-git-users who can follow the rename instructions manually (or fix up their patch utility) if they insist on shunning tools that would make their life easier.
quoted hunk ↗ jump to hunk
diff --git a/arch/powerpc/kernel/dma.c b/arch/powerpc/kernel/dma.c new file mode 100644 index 0000000..ae5708e[...]diff --git a/arch/powerpc/kernel/dma_64.c b/arch/powerpc/kernel/dma_64.c deleted file mode 100644 index ae5708e..0000000That is, if hashes match then it was pure rename.
I suppose, though it's not as easy to spot, and won't help in showing what the differences are if there are any. -Scott