From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
Philip Oakley <philipoakley@iee.org>,
git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: [PATCH 3/3] clone: add `--seed` shorthand
Date: Sun, 24 May 2015 12:07:53 -0700 [thread overview]
Message-ID: <xmqqtwv1bxpy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150522064922.GA27716@peff.net> (Jeff King's message of "Fri, 22 May 2015 02:49:23 -0400")
Jeff King <peff@peff.net> writes:
> Having slept on it, I really think "--seed" should be "fetch from the
> seed into temp refs", and not what I posted earlier.
Yeah, I think that is the right way to do it.
And it happens to mesh well with the (not so well advertised but not
so well hidden) plan to allow loaded server side to advise --seed
from bundle hosted elsewhere, e.g.
* "clone" connects to upload-pack
* upload-pack advertises --seed=http://cdn.github.com/project.bundle
via capability
* "clone" disconnects from upload-pack, and runs (resumable)
wget to the seed to grab bundle.
* "clone" then fetches refs/*:refs/remotes/origin/* from the bundle
* "clone" then continues to fetch into +refs/remotes/origin/* as
usual, but does an equivalent of using --prune for this fetch
to drop anything extra/stale that the seed bundle may have
had.
* optionally "clone" can immediately "repack".
... which I wanted to see happen in a near future.
And that --seed thing that can name a local bundle file is a very
good first step toward the direction, I think.
Thanks.
next prev parent reply other threads:[~2015-05-24 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 4:14 [PATCH/RFC 0/3] --seed as an alias for --dissociate --reference Jeff King
2015-05-21 4:15 ` [PATCH 1/3] clone: use OPT_STRING_LIST for --reference Jeff King
2015-05-21 4:16 ` [PATCH 2/3] clone: reorder --dissociate and --reference options Jeff King
2015-05-21 4:16 ` [PATCH 3/3] clone: add `--seed` shorthand Jeff King
2015-05-21 16:05 ` Johannes Schindelin
2015-05-21 19:45 ` Philip Oakley
2015-05-22 6:37 ` Johannes Schindelin
2015-05-22 6:49 ` Jeff King
2015-05-24 19:07 ` Junio C Hamano [this message]
2015-05-27 8:19 ` Jeff King
2015-05-27 19:35 ` Junio C Hamano
2015-05-22 6:50 ` Jeff King
2015-05-21 5:01 ` [PATCH/RFC 0/3] --seed as an alias for --dissociate --reference Junio C Hamano
2015-05-21 5:06 ` Jeff King
2015-05-21 16:41 ` Junio C Hamano
2015-05-24 23:53 ` Michael Haggerty
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=xmqqtwv1bxpy.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=philipoakley@iee.org \
/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).