From: Yann COLLETTE <ycollette.nospam@free.fr>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: Problem while cloning a git repo
Date: Wed, 13 Nov 2013 08:58:33 +0100 [thread overview]
Message-ID: <52833129.6060707@free.fr> (raw)
In-Reply-To: <20131113002035.GK183446@vauxhall.crustytoothpaste.net>
Hello,
When I perform the git clone via git, it works. The problem is only
happening via http.
I tried to play with http.postBuffer and I set this parameter to it's
maximum (a little bit before a git clone triggered a memory alloc
problem) and I see that something big is trying to be downloaded. But I
don't see such a big file in my history of commits. The maximum one
seems to be around 50 Mo ...
Le 13/11/2013 01:20, brian m. carlson a écrit :
> On Tue, Nov 12, 2013 at 01:50:24PM +0100, ycollette.nospam@free.fr wrote:
>> Hello,
>>
>> When I clone a repository, I get an error from git:
>>
>> git clone http://192.168.0.18:8080/test test_Gerrit
>> Clonage dans 'test_Gerrit'...
>> remote: Counting objects: 25106, done
>> remote: Finding sources: 100% (25106/25106)
>> error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s
> curl code 56 is a receive error (CURLE_RECV_ERROR). It sounds like
> you're encountering some sort of network error or broken proxy. Does
> cloning this repository over the git protocol or SSH work, or can you
> try it over https (to avoid the proxy)?
>
next prev parent reply other threads:[~2013-11-13 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 12:50 Problem while cloning a git repo ycollette.nospam
2013-11-13 0:20 ` brian m. carlson
2013-11-13 7:58 ` Yann COLLETTE [this message]
[not found] ` <52832DA0.7040108@free.fr>
2013-11-13 23:40 ` brian m. carlson
2013-11-14 8:20 ` Yann COLLETTE
2013-11-18 7:31 ` ycollette.nospam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52833129.6060707@free.fr \
--to=ycollette.nospam@free.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.