git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Muzaffer Tolga Ozses <tolga@ozses.net>
Cc: Konstantin Khomoutov <flatworm@users.sourceforge.net>,
	git@vger.kernel.org
Subject: Re: Git reports
Date: Fri, 6 Dec 2013 11:26:51 -0800	[thread overview]
Message-ID: <20131206192651.GK29959@google.com> (raw)
In-Reply-To: <CAMAQ3nLgnpDo1jWFL1rqtEvmQm8LeEpZ41Uxo0GTQOk8ttpSZA@mail.gmail.com>

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 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.

Perhaps we can document this better?  (If so, where would it have been
useful to learn about this, and do you have ideas for how it could be
worded?  I'm thinking it might make sense to put a note on this in a
new giturls(7) page with content that used to be in the git-clone(1)
'GIT URLS' section.)  Or if someone wants to work on a progress
display, that would be nice, too. ;-)

Thanks and hope that helps,
Jonathan

  parent reply	other threads:[~2013-12-06 19:27 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 [this message]
2013-12-06 20:36             ` Junio C Hamano
2013-12-06 22:22             ` Jeff King
2013-12-07 19:46               ` Muzaffer Tolga Ozses

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=20131206192651.GK29959@google.com \
    --to=jrnieder@gmail.com \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=tolga@ozses.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).