git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Kevin Wern <kevin.m.wern@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Resumable clone
Date: Sat, 05 Mar 2016 10:40:01 -0800	[thread overview]
Message-ID: <xmqqk2lgvke6.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqoaasvkrt.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Sat, 05 Mar 2016 10:31:50 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> So what remains?  Here is a rough and still slushy outline:
>
>  - A new method, prime_clone(), in "struct transport" for "git
>    clone" client to first call to learn the location of the
>    "alternate resource" from the server.
>
>    ...
>    - The format of the returned "answer" needs to be designed.  It
>      must be able to express:
>
>      - the location of the resource, i.e. a URL;
>
>      - the type of resource, if we want this to be extensible.  I
>        think we should initially limit it to "a single full history
>        .pack", so from that point of view this may not be absolutely
>        necessary, but we already know that we may want to say "go
>        there and you will find an old-style bundle file" to support
>        the kernel.org CDN, and we may also want to support Jeff's
>        "split bundle" or Shawn's ".info" file.  A resource poor
>        (read: personal) machine that hosts a personal of a popular

Sorry for a typo: s/of a/fork &/;

>        project might want to name a "git clone" URL for that popular
>        project it forked from (e.g. "Clone Linus's repository from
>        kernel.org and then come back here for incremental fetch").

  reply	other threads:[~2016-03-05 18:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  9:23 Resumable clone Kevin Wern
2016-03-05  9:40 ` Duy Nguyen
2016-03-05 18:31   ` Junio C Hamano
2016-03-05 18:40     ` Junio C Hamano [this message]
2016-03-06  7:59     ` Johannes Schindelin
2016-03-06  8:49       ` Duy Nguyen
2016-03-06  8:52         ` Duy Nguyen
2016-03-06 19:48         ` Junio C Hamano
2016-03-07  3:55       ` Junio C Hamano
2016-03-08  3:33     ` Kevin Wern
2016-03-08 11:11       ` Duy Nguyen
2016-03-08 17:25         ` Junio C Hamano
2016-03-08 17:07       ` Junio C Hamano
2016-03-09  2:04         ` Kevin Wern

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=xmqqk2lgvke6.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kevin.m.wern@gmail.com \
    --cc=pclouds@gmail.com \
    /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).