Jakobus Schürz <wertstoffe@xxxxxxxxxxxxxx> writes: > Does anyone has an idea? Lack of response generally indicate that people are not interested but the reason why they are not varies. It may be because you did not give them sufficient information about your situation (are you trying to do this on Windows, for example?). It may be because you are looking for a solution that applies only to a narrow situation that they are not interested in, but by stepping back a bit and by coming up with a solution that may apply to more general problem may pique their interest. Instead of patching "git" to tell it what the connection timeout is, perhaps a more general command that runs anything and aborts it if it does not finish within given time period, e.g. timeout 180 git ls-remote <REMOTE> may run "git ls-remote <REMOTE>" but kill it if it does not finish within 180 seconds. If you wrote such a general purpose command, that would help you running ls-remote and abort it if it does not finish within the given timeout, and also help others who are not using Git but with a similar need to run other things and kill them when they run for too long. Who knows. If you look for such a command, you might find that one already exists. http://lmgtfy.com/?q=run+linux+command+with+timeout
