git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: Craig Schlenter <craig@codefountain.com>,
	Junio C Hamano <junkio@cox.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Make "git clone" less of a deathly quiet experience
Date: Sat, 11 Feb 2006 14:05:30 +0100	[thread overview]
Message-ID: <20060211130530.GR31278@pasky.or.cz> (raw)
In-Reply-To: <43EDA3D0.7090204@gorzow.mm.pl>

Dear diary, on Sat, Feb 11, 2006 at 09:44:00AM CET, I got a letter
where Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> said that...
> Craig Schlenter wrote:
> > On 11 Feb 2006, at 7:48 AM, Junio C Hamano wrote:
> > It would be nice if the "partial pack" or whatever that has been
> > downloaded at the time of the breakage could be re-used and
> > things could start "from that point onwards" or the bits that were
> > already received could be unpacked. Comments?
> 
> It even already works on plain http repos with git fetch.
> (e.g. WineHQ repository)
> Why git protocol doesn't support it?

Because it works totally different. When downloading from plain HTTP
repos, you are just downloading files from the remote repository and it
is easy to pick up wherever you left (and last night, I just added a
possibility to Cogito to resume an interrupted cg-clone by just cd'ing
inside and running cg-fetch, as is; it's pretty neat) - you just resume
downloading of the file you downloaded last, and don't download again
the files you already have.

But the native git protocol works completely differently - you tell the
server "give me all objects you have between object X and head", the
object will generate a completely custom pack just for you and send it
over the network. The next time you fetch, you just ask for a pack
between object X and head again, but the head can be already totally
different. What we would have to do is to check for interrupted
packfiles before fetching, attempt to fix them (cutting out the
incomplete objects and broken delta chains, if applicable), and then
tell the remote side to skip those objects; but that may not be easy
because there can be a lot of "loose fibres". Another way would be to
just tell the server "if head is still Y, start sending the pack only
after N bytes". *shudder*

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe.  -- Douglas Adams

  reply	other threads:[~2006-02-11 13:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  4:31 Make "git clone" less of a deathly quiet experience Linus Torvalds
2006-02-11  4:37 ` Linus Torvalds
2006-02-11  5:50   ` Junio C Hamano
2006-02-11 17:39     ` Linus Torvalds
2006-02-11  5:48 ` Junio C Hamano
2006-02-11  7:35   ` Craig Schlenter
2006-02-11  8:44     ` Radoslaw Szkodzinski
2006-02-11 13:05       ` Petr Baudis [this message]
2006-02-11 13:15         ` Radoslaw Szkodzinski
2006-02-11 13:33   ` Petr Baudis
2006-02-11 13:41     ` Petr Baudis
2006-02-11 17:24     ` Alex Riesen
2006-02-11 17:45   ` Linus Torvalds
2006-02-11 19:10     ` Keith Packard
2006-02-12  3:43       ` Andreas Ericsson
2006-02-12  4:11         ` Keith Packard
2006-02-12 11:02           ` Andreas Ericsson
2006-02-12 21:04             ` Keith Packard
2006-02-16  6:56             ` Eric W. Biederman
2006-02-16  7:33               ` Junio C Hamano
2006-02-13  2:06           ` Martin Langhoff
2006-02-13  3:36             ` Junio C Hamano
2006-02-11 18:39 ` Alex Riesen
2006-02-11 19:04   ` Linus Torvalds

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060211130530.GR31278@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=astralstorm@gorzow.mm.pl \
    --cc=craig@codefountain.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).