From: Sam Ravnborg <hidden> Date: 2016-06-15 22:43:44
I just stumbled on what looks like a simple bug in git apply.
I had following diff:
diff --git a/arch/i386/defconfig b/arch/x86/configs/i386_defconfigsimilarity index 100%rename from arch/i386/defconfigrename to arch/x86/configs/i386_defconfigdiff --git a/arch/x86_64/defconfig b/arch/x86/configs/x86_64_defconfigsimilarity index 100%rename from arch/x86_64/defconfigrename to arch/x86/configs/x86_64_defconfig
--
1.5.3.4.1157.g0e74-dirty
When trying to apply this diff using:
git apply -p1 < .../patch
I noticed that the two defconfig files were deleted as expected,
but the renamed versions did not appear in the arch/x86/configs/
directory.
The configs/ directory did not exist and was not created.
Without looking at git apply I assume that the rename failed because
it is not prepared to rename a file to a directory that does not exist.
Buried in other stuff so I did not take a look myself..
Sam
From: Alex Riesen <hidden> Date: 2016-06-15 22:43:44
Sam Ravnborg, Thu, Oct 25, 2007 20:07:37 +0200:
quoted hunk
I just stumbled on what looks like a simple bug in git apply.
I had following diff:
diff --git a/arch/i386/defconfig b/arch/x86/configs/i386_defconfigsimilarity index 100%rename from arch/i386/defconfigrename to arch/x86/configs/i386_defconfigdiff --git a/arch/x86_64/defconfig b/arch/x86/configs/x86_64_defconfigsimilarity index 100%rename from arch/x86_64/defconfigrename to arch/x86/configs/x86_64_defconfig
--
1.5.3.4.1157.g0e74-dirty
When trying to apply this diff using:
git apply -p1 < .../patch
From: Alex Riesen <hidden> Date: 2016-06-15 22:43:44
Alex Riesen, Thu, Oct 25, 2007 23:30:38 +0200:
Sam Ravnborg, Thu, Oct 25, 2007 20:07:37 +0200:
quoted
I just stumbled on what looks like a simple bug in git apply.
I had following diff:
diff --git a/arch/i386/defconfig b/arch/x86/configs/i386_defconfigsimilarity index 100%rename from arch/i386/defconfigrename to arch/x86/configs/i386_defconfigdiff --git a/arch/x86_64/defconfig b/arch/x86/configs/x86_64_defconfigsimilarity index 100%rename from arch/x86_64/defconfigrename to arch/x86/configs/x86_64_defconfig
--
1.5.3.4.1157.g0e74-dirty
.1157...-dirty. Your git looks heavily modified. Could you try with a
something like master of kernel.org?
Mine is based off d90a7fda355c251b8ffdd79617fb083c18245ec2
(builtin-fetch got merged).
quoted
When trying to apply this diff using:
git apply -p1 < .../patch
From: Sam Ravnborg <hidden> Date: 2016-06-15 22:43:44
On Thu, Oct 25, 2007 at 11:35:23PM +0200, Alex Riesen wrote:
Alex Riesen, Thu, Oct 25, 2007 23:30:38 +0200:
quoted
Sam Ravnborg, Thu, Oct 25, 2007 20:07:37 +0200:
quoted
I just stumbled on what looks like a simple bug in git apply.
I had following diff:
diff --git a/arch/i386/defconfig b/arch/x86/configs/i386_defconfigsimilarity index 100%rename from arch/i386/defconfigrename to arch/x86/configs/i386_defconfigdiff --git a/arch/x86_64/defconfig b/arch/x86/configs/x86_64_defconfigsimilarity index 100%rename from arch/x86_64/defconfigrename to arch/x86/configs/x86_64_defconfig
--
1.5.3.4.1157.g0e74-dirty
.1157...-dirty. Your git looks heavily modified. Could you try with a
something like master of kernel.org?
I guess I still have Linus' rename stuff added - will update.
Mine is based off d90a7fda355c251b8ffdd79617fb083c18245ec2
(builtin-fetch got merged).
quoted
quoted
When trying to apply this diff using:
git apply -p1 < .../patch
works here. Don't use -p1, it is assumed
It seems to be a picnic[*] bug - at least I cannot reproduce it.
Sorry for the noise but thanks for testing.
[*] Problem In Chair Not In Computer
Sam