Jörn Engel <joern@xxxxxxxxxxxxxxx> writes: > Something weird happened to us and I have no idea how to reproduce it. > A developer managed to create a git commit with the following content: > > diff --git a/foo b/foo > new file mode 160000 > index 000000000000..b7e7816c1266 > --- /dev/null > +++ b/foo > @@ -0,0 +1 @@ > +one line of content > > File name and content obfuscated, the rest is verbatim from the git > commit. > > Now, file mode 160000 doesn't make sense to me. These are gitlinks, that are used to implement submodules. I cannot tell if this is an expected behaviour and there is nothing to worry about, or you found a corner case bug, without looking at what the "one line of content" says, but if it says "Subproject commit " followed by 40-hex object name, then that is a perfectly normal behaviour. After doing these: git init bar cd bar git init foo cd foo ;# in bar/foo git commit --allow-empty -m initial cd .. ;# back in bar git add foo git commit -m add git show anybody who has a working Git would see the "diff --git" that shows 160000 you showed above.
