From: Jeff King <peff@peff.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Alexander Miseler <alexander@miseler.de>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Christian Couder <chriscool@tuxfamily.org>,
Thomas Rast <trast@student.ethz.ch>, git <git@vger.kernel.org>,
Pranav Ravichandran <prp.1111@gmail.com>
Subject: Re: GSoC resumable clone
Date: Fri, 11 Mar 2011 10:48:22 -0500 [thread overview]
Message-ID: <20110311154822.GA30605@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTi=D5kYh-w-6CKuCf39fnH1SYT5HxJ31tdq2vb9d@mail.gmail.com>
On Fri, Mar 11, 2011 at 07:41:14AM -0800, Shawn O. Pearce wrote:
> > I think there is room for both ideas. The cached bundle idea is not just
> > "here, download this bundle first". It is "here, download this _other
> > thing_ first, which might be a bundle, another git repo, a torrent,
> > etc".
>
> Fair enough. Though I wouldn't limit this to bundles. Instead I would
> suggest supporting any valid Git URLs, and then extend our URL syntax
> to support bundles over http://, rsync://, and torrent.
Sorry, I didn't mean to imply that it was limited to bundles. It would
support arbitrary URLs or schemes. See this thread for some past
discussion:
http://article.gmane.org/gmane.comp.version-control.git/164700
> If we support any URL and don't assume the URL is a bundle, you can
> point traffic at kernel.org to for example grab Linus' primary
> repository first, even if he doesn't have a bundle.
Exactly.
-Peff
next prev parent reply other threads:[~2011-03-11 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 15:17 GSoC resumable clone Shawn Pearce
2011-03-11 15:37 ` Jeff King
2011-03-11 15:41 ` Shawn Pearce
2011-03-11 15:48 ` Jeff King [this message]
2011-03-11 20:50 ` Ilari Liusvaara
2011-03-11 21:43 ` Jeff King
2011-03-11 15:42 ` Nguyen Thai Ngoc Duy
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=20110311154822.GA30605@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Jens.Lehmann@web.de \
--cc=alexander@miseler.de \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=prp.1111@gmail.com \
--cc=spearce@spearce.org \
--cc=trast@student.ethz.ch \
/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).