From: Junio C Hamano <gitster@pobox•com>
To: "Philip Oakley" <philipoakley@iee•org>
Cc: <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Mar 2016, #04; Wed, 23)
Date: Thu, 24 Mar 2016 09:14:30 -0700 [thread overview]
Message-ID: <xmqqlh57am55.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <54B6C1E1FE6A4BAEA07E97B7BA81EB01@PhilipOakley> (Philip Oakley's message of "Thu, 24 Mar 2016 07:42:07 -0000")
"Philip Oakley" <philipoakley@iee•org> writes:
>>
>> The beginning of "split bundle", which could be one of the
>> ingredients to allow "git clone" traffic off of the core server
>> network to CDN.
>>
> ...
> Hi Junio,
>
> I think there may be a concept clash between the ideals of a
> sneakernet bundle' and the 'resumable clone'.
Notice the "could" above ;-)
Read the original thread and notice that the inclination is for the
first one the primary "clone priming" mechanism would likely to be a
packfile, not a bundle, even though use of "bundle" is not ruled out.
next prev parent reply other threads:[~2016-03-24 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 21:12 What's cooking in git.git (Mar 2016, #04; Wed, 23) Junio C Hamano
2016-03-24 7:42 ` Philip Oakley
2016-03-24 16:14 ` Junio C Hamano [this message]
2016-03-24 21:47 ` Philip Oakley
2016-03-24 21:51 ` Junio C Hamano
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=xmqqlh57am55.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=philipoakley@iee$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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