On Sat, Nov 23, 2013 at 05:36:36PM +0100, Stefan Beller wrote: > sb@sb:/tmp$ git clone https://github.com/Bertram25/ValyriaTear.git > Cloning into 'ValyriaTear'... > remote: Counting objects: 21346, done. > remote: Compressing objects: 100% (6307/6307), done. > remote: Total 21346 (delta 16463), reused 19820 (delta 15000) > Receiving objects: 100% (21346/21346), 176.39 MiB | 445.00 KiB/s, done. > Resolving deltas: 100% (16463/16463), done. > Checking connectivity... done. > error: git-remote-https died of signal 13 > > However the repository seems to be cloned fine. > I can clone different repos from github and they are working fine > without the error. > Would that be an issue on my side or on githubs side? Almost certainly on your side. 13 is SIGPIPE, so git-remote-https is trying to write something but the other side of the pipe has hung up. This might be a race condition in the transport-helper protocol, where we've had similar problems before. It doesn't reproduce here for me. Can you reproduce it consistently on this repo? I would not be at all surprised if it is intermittent. If you can reproduce, it would be interesting to see the output with GIT_TRANSPORT_HELPER_DEBUG=1, or even with "strace -f". That could at least tell us what it was trying to write (and to where) when it got the SIGPIPE. -Peff -- 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