23 Feb
2012
23 Feb
'12
3:38 p.m.
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
On Thu, Feb 23, 2012 at 8:23 PM, David C. Rankin <
drankinatty(a)suddenlinkmail.com> wrote:
Tim, all,
I am working on build scripts that will individually pull or update the
source
by pulling code from the git tree. To make this more efficient for building
individual modules (and reduce unneeded bandwidth), it is recommended to
use the
git clone form:
git clone --depth 1 http://scm.trinitydesktop.org/scm/git/whatever
But http://scm.trinitydesktop.org/scm/git/ refuses to allow '--depth 1'
to be
used in the git clone. Anybody know why? The error received is:
Cloning into 'libart-lgpl'...
error: RPC failed; result=22, HTTP code = 500
fatal: The remote end hung up unexpectedly
It works fine without the --depth limitation. What say the 'git' masters?
--
David C. Rankin, J.D.,P.E.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
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