I was using the latest git version 2.6.2 already.
I suspect it is due to a .gitconfig. This is what is probably required:
➜ ~ cat .gitconfig
[diff]
submodule = log
On 28/10/15 13:24, Victor Leschuk wrote:
On 10/28/2015 02:58 PM, Mathias L. Baumann wrote:
Hello dear git devs,
I just stumbled upon a segfault when doing just "git diff" in my repo.
I managed to create a minimal repo setup where the bug is reproducable.
The problem seems to be a mix of having an untracked submodule and
having set an alternates file for one submodule.
Attached you'll find my setup that will reproduce the problem. Simply
run 'git diff' in bugtest1.
In case the attachment is refused, I also uploaded it here:
http://supraverse.net/bugdemo.tar.gz
cheers,
--Marenz
Hello Marenz,
I have just tried to reproduce segfault with the provided archive:
[del@del-debian bugtest1 (master)]$ git diff
diff --git a/submodules/bugtest2 b/submodules/bugtest2
--- a/submodules/bugtest2
+++ b/submodules/bugtest2
@@ -1 +1 @@
-Subproject commit cd0b9ee2946d2df3626943347332a4d86f93b126
+Subproject commit cd0b9ee2946d2df3626943347332a4d86f93b126-dirty
No segfault occured. I am using
git version 2.6.2.308.g3b8f10c
Could you please specify which version of git you are using and also try
to reproduce it with latest 2.6.2?
--
Victor
--
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