From: Jeff King <peff@peff.net>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Zenaan Harkness <zen@freedbms.net>,
git@vger.kernel.org
Subject: Re: Resumable clone/Gittorrent (again) - stable packs?
Date: Fri, 7 Jan 2011 17:27:04 -0500 [thread overview]
Message-ID: <20110107222704.GA10583@sigill.intra.peff.net> (raw)
In-Reply-To: <20110107222133.GA2377@LK-Perkele-VI.localdomain>
On Sat, Jan 08, 2011 at 12:21:33AM +0200, Ilari Liusvaara wrote:
> On Fri, Jan 07, 2011 at 04:56:31PM -0500, Jeff King wrote:
> > On Fri, Jan 07, 2011 at 11:45:01PM +0200, Ilari Liusvaara wrote:
> >
> >
> > I think there should always be an assumption that mirrors are not
> > necessarily complete. That is necessary for bundle-like mirrors to be
> > feasible, since updating the bundle for every commit defeats the
> > purpose.
>
> Also add protocol that grabs a bundle from HTTP and then opens that
> up? :-)
Well, yes, that still needs to be implemented. But it's all client-side,
so the server just has to provide the bundle somewhere.
> > It would be nice for there to be a way for some mirrors to be marked as
> > "should be considered complete and authoritative", since we can optimize
> > out the final check of the master in that case (as well as for future
> > fetches). But that's a future feature. My plan was to leave space in the
> > mirror list for arbitrary metadata of that sort.
>
> The first thing one should get/do when connecting to another repository
> is its list of references. One can see from there if what one has got
> is complete or not (with --use-mirror that only allows skipping commit
> negotiation and fetch, not the whole connection due to the fact that the
> repositories are contacted in order)...
Yes, but it would be cool to be able to skip even that connect in some
cases (e.g., mirrors can be useful not just to take load off the master,
but also when the master isn't available, either for downtime or because
the client is behind a firewall). But the default should definitely be
to double-check that the master is right, and we can leave more advanced
cases for later (we just need to be aware of leaving room for them now).
I'm going to start working on a patch series for this, so hopefully
we'll see how it's shaping up in a day or two.
-Peff
next prev parent reply other threads:[~2011-01-07 22:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 2:29 Resumable clone/Gittorrent (again) - stable packs? Zenaan Harkness
2011-01-06 17:05 ` Shawn Pearce
2011-01-10 16:39 ` John Wyzer
2011-01-10 21:42 ` Sam Vilain
2011-01-11 0:03 ` Nguyen Thai Ngoc Duy
2011-01-11 0:57 ` J.H.
2011-01-11 1:56 ` Nguyen Thai Ngoc Duy
2011-01-06 21:09 ` Nicolas Pitre
2011-01-07 2:36 ` Zenaan Harkness
2011-01-07 4:33 ` Nicolas Pitre
2011-01-07 5:22 ` Jeff King
2011-01-07 5:31 ` Jeff King
2011-01-07 10:04 ` Zenaan Harkness
2011-01-07 18:52 ` Ilari Liusvaara
2011-01-07 19:17 ` Jeff King
2011-01-07 21:45 ` Ilari Liusvaara
2011-01-07 21:56 ` Jeff King
2011-01-07 22:21 ` Ilari Liusvaara
2011-01-07 22:27 ` Jeff King [this message]
2011-01-10 21:07 ` Sam Vilain
2011-01-10 11:48 ` Nguyen Thai Ngoc Duy
2011-01-10 13:50 ` Nicolas Pitre
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=20110107222704.GA10583@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=nico@fluxnic.net \
--cc=zen@freedbms.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).