Ralf Baechle <ralf@xxxxxxxxxxxxxx> writes:
>> diff --git a/arch/mips/boot/dts/include/dt-bindings b/arch/mips/boot/dts/include/dt-bindings
>> index 68ae388..08c00e4 120000
>> --- a/arch/mips/boot/dts/include/dt-bindings
>> +++ b/arch/mips/boot/dts/include/dt-bindings
>> @@ -1 +1 @@
>> -../../../../../include/dt-bindings
>> +../../../../../include/dt-bindings
>> \ No newline at end of file
>> --
>> 1.7.10.4
>
> I applied your patch - but now git-show shows it as an empty commit and
>
> ls -lb arch/mips/boot/dts/include/dt-bindings
>
> still shows the \n at the end of the link target.
> ...
> So, I wonder if this is a git bug.
Sounds as if "git am" is losing the important bit of information
that new content ends with an incomplete line.
However, it does not reproduce for me.
$ rm -fr /var/tmp/x && mkdir /var/tmp/x && cd /var/tmp/x
$ git init
$ ln -s 'a
' b
$ git add b
$ git commit -m initial
$ ln -f -s a b
$ git add b
$ git commit -m fix
$ git format-patch -1
$ git checkout HEAD^
$ git am 0001-*
$ git diff HEAD^ HEAD
diff --git a/b b/b
index 7898192..2e65efe 120000
--- a/b
+++ b/b
@@ -1 +1 @@
-a
+a
\ No newline at end of file
I see the same with v1.7.10 (which may not match your version;
v1.7.10.4 is what was used by the patch submitter to prepare the
patch, and you did not say how you are applying the patches in your
message) and with more recent Git. There is no such breakage.
I briefly suspected that you might be passing "--whitespace=fix" to
"am" and that may be incorrectly "fixing" the incomplete line, but
that is not the case. I get the same result if I add the option to
"am" in the above transcript.
How are you applying the patch? What is your Git version?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html