From: Muzaffer Tolga Ozses <tolga@ozses.net>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Konstantin Khomoutov <flatworm@users.sourceforge.net>,
git@vger.kernel.org
Subject: Re: Git reports
Date: Sat, 7 Dec 2013 21:46:16 +0200 [thread overview]
Message-ID: <CAMAQ3nK3CMvhh2=wYqCedd_9fS9k9yGWdmN8NzRfQft585zigQ@mail.gmail.com> (raw)
In-Reply-To: <20131206222201.GF25620@sigill.intra.peff.net>
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 <peff@peff.net> 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 "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.
>
> Yeah, that would also explain why GIT_TRACE_PACKET produced no output.
>
>> Perhaps the client should do some progress reporting based on file
>> sizes and amount downloaded so far, but it's hard to get excited
>> about given the existence of "smart" (transfer only what is needed)
>> HTTP protocol. See git-http-backend(1) for details.
>
> You get some very verbose and nasty progress with "-vv". It would be
> nice to have a regular throughput meter for dumb-http, though. I haven't
> bothered adding one so far because I don't expect many people are using
> http. However, if we start supporting fetching via bundles over http,
> then it will be very nice to have some kind of progress display there
> (since the main use is to get gigantic full clones).
>
> -Peff
prev parent reply other threads:[~2013-12-07 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:51 Git reports Muzaffer Tolga Ozses
2013-12-06 17:00 ` Konstantin Khomoutov
2013-12-06 17:09 ` Konstantin Khomoutov
2013-12-06 17:44 ` Muzaffer Tolga Ozses
2013-12-06 17:50 ` Jeff King
2013-12-06 17:53 ` Konstantin Khomoutov
2013-12-06 19:19 ` Muzaffer Tolga Ozses
2013-12-06 19:24 ` Muzaffer Tolga Ozses
2013-12-06 19:26 ` Jonathan Nieder
2013-12-06 20:36 ` Junio C Hamano
2013-12-06 22:22 ` Jeff King
2013-12-07 19:46 ` Muzaffer Tolga Ozses [this message]
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='CAMAQ3nK3CMvhh2=wYqCedd_9fS9k9yGWdmN8NzRfQft585zigQ@mail.gmail.com' \
--to=tolga@ozses.net \
--cc=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).