I looked at man git-http-backend, and I didn't understand a thing.
I'll look at it tomorrow again with a clear head.
On 7 December 2013 00:22, Jeff King wrote:
> On Fri, Dec 06, 2013 at 11:26:51AM -0800, Jonathan Nieder wrote:
>
>> > I am cloning over http
>>
>> I am guessing you are using the "d
On Fri, Dec 06, 2013 at 11:26:51AM -0800, Jonathan Nieder wrote:
> > I am cloning over http
>
> I am guessing you are using the "dumb" (plain static file transfer)
> HTTP protocol. With that protocol the server doesn't do anything
> other than shuttle out files, so it doesn't need to do its own
Jonathan Nieder writes:
> Muzaffer Tolga Ozses wrote:
>
>> I am cloning over http
>
> I am guessing you are using the "dumb" (plain static file transfer)
> HTTP protocol. With that protocol the server doesn't do anything
> other than shuttle out files, so it doesn't need to do its own
> progress
Muzaffer Tolga Ozses wrote:
> I am cloning over http
I am guessing you are using the "dumb" (plain static file transfer)
HTTP protocol. With that protocol the server doesn't do anything
other than shuttle out files, so it doesn't need to do its own
progress reporting.
Perhaps the client should
Sorry, my git server is on CentOS and git 1.8.4.2 and my machine on
which I clone is Ubuntu, 1.8.3.2
On 6 December 2013 21:19, Muzaffer Tolga Ozses wrote:
> Hi,
>
>> What protocol/transport are you using (http, ssh, git)?
> I am cloning over http
>
>> Can you try running with:
>
> GIT_TRACE_PACK
Hi,
> What protocol/transport are you using (http, ssh, git)?
I am cloning over http
> Can you try running with:
GIT_TRACE_PACKET=$PWD/trace.out git clone ...
GIT_TRACE_PACKET=$PWD/trace.out git clone
http://git.webciniz.im/project/night_pharmacy.git
Cloning into 'night_pharmacy'...
Checking co
On Fri, 6 Dec 2013 19:44:21 +0200
Muzaffer Tolga Ozses wrote:
[...]
> >> > Resolving deltas: 100% (369/369), done.
> >> >
> >> > whereas I don't get those with my own. What could I be doing
> >> > wrong?
[...]
> >> So it might turn out on your own server Git for some reason fails
> >> to figure o
On Fri, Dec 06, 2013 at 07:44:21PM +0200, Muzaffer Tolga Ozses wrote:
> stty tells me
> speed 38400 baud; line = 0;
> eol = M-^?; eol2 = M-^?; swtch = M-^?;
> ixany iutf8
>
> And I run identical commands on both servers, only URL changes.
What protocol/transport are you using (http, ssh, git)?
stty tells me
speed 38400 baud; line = 0;
eol = M-^?; eol2 = M-^?; swtch = M-^?;
ixany iutf8
And I run identical commands on both servers, only URL changes.
On 6 December 2013 19:09, Konstantin Khomoutov
wrote:
> On Fri, 6 Dec 2013 21:00:35 +0400
> Konstantin Khomoutov wrote:
>
> [...]
>> > Res
On Fri, 6 Dec 2013 21:00:35 +0400
Konstantin Khomoutov wrote:
[...]
> > Resolving deltas: 100% (369/369), done.
> >
> > whereas I don't get those with my own. What could I be doing wrong?
>
> The documentation on `git push` states:
>
> --progress
>
> Progress status is reported on the s
On Fri, 6 Dec 2013 18:51:47 +0200
Muzaffer Tolga Ozses wrote:
> On another git server, I get reports like
> Cloning into 'tcmb'...
> remote: Counting objects: 704, done.
> remote: Compressing objects: 100% (574/574), done.
> remote: Total 704 (delta 369), reused 107 (delta 60)
> Receiving objects
Hi,
On another git server, I get reports like
Cloning into 'tcmb'...
remote: Counting objects: 704, done.
remote: Compressing objects: 100% (574/574), done.
remote: Total 704 (delta 369), reused 107 (delta 60)
Receiving objects: 100% (704/704), 129.99 KiB | 23 KiB/s, done.
Resolving deltas: 100% (
12 matches
Mail list logo
