If this is the case you could perhaps try downgrading git. I have seen this problem with newer git. Also if https is supported, try it.


On Thu, Feb 23, 2012 at 9:46 PM, David C. Rankin <drankinatty@...> wrote:
On 02/23/2012 05:38 PM, Jay wrote:
> Firstly i have to say that my git jitsu is not strong.
> Is the received immediately or after some time of hanging?
> If the former i would suspect a problem with the handshake while using a shallow
> scope. In the latter case it could be timing out because of the size of the tree
> or a particular file in the tree. This can happen when pushing larger git files
> over http protocol. Perhaps you could try adding something like: git config
> http.postBuffer 524288000
> Try using https if it is supported.
> Jay


 This happens immediately. You don't have time to blink and you get the error:

Cloning into 'libart-lgpl'...
error: RPC failed; result=22, HTTP code = 500
fatal: The remote end hung up unexpectedly

 So I think your suspicion of "a problem with the handshake while using a
shallow scope" is right on. Since I learned git a few days ago, your git jitsu
has much "more focus" than mine :)

David C. Rankin, J.D.,P.E.

To unsubscribe, e-mail: trinity-devel-unsubscribe@...
For additional commands, e-mail: trinity-devel-help@...
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting