From: "Philip Oakley" <philipoakley@iee.org>
To: "Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Jeff King" <peff@peff.net>
Cc: <git@vger.kernel.org>, "Michael Haggerty" <mhagger@alum.mit.edu>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 3/3] clone: add `--seed` shorthand
Date: Thu, 21 May 2015 20:45:18 +0100 [thread overview]
Message-ID: <3516DC60279A42188EE2AA394921FC70@PhilipOakley> (raw)
In-Reply-To: 8895881cd3f324d2b8a827e311296a48@www.dscho.org
From: "Johannes Schindelin" <johannes.schindelin@gmx.de>
> Hi Peff,
>
> On 2015-05-21 06:16, Jeff King wrote:
>
>> diff --git a/Documentation/git-clone.txt
>> b/Documentation/git-clone.txt
>> index f1f2a3f..ffeb03b 100644
>> --- a/Documentation/git-clone.txt
>> +++ b/Documentation/git-clone.txt
>> @@ -107,6 +107,9 @@ objects from the source repository into a pack in
>> the cloned repository.
>> transfer and stop borrowing from them after a clone is made
>> by making necessary local copies of borrowed objects.
>>
>> +--seed <repository>::
>> + A convenient shorthand for `--dissociate --reference=<repository>`.
>> +
>
> Since you want to advertise this as an easier way than
> `--dissociate --reference=<repository>`, it might make sense to avoid
> sending the reader that way, too.
>
> Maybe something like
>
> --seed <repository>::
> Fetch objects from <repository> instead of the clone URL when
> possible. This is useful when a (possibly partial) clone already
> exists locally, to avoid transferring the same objects again.
>
Would it be worth mentioning here that a bundle is a satisfactory
alternative to repository?
+--seed <repository|bundle>::
+ Fetch objects from <repository> or <bundle> instead of the clone
URL when possible. This is useful when a (possibly partial) clone
already exists locally, to avoid transferring the same objects again.
I haven't checked if the invocation would accept a bundle filename, but
I'm presuming it can in the same way that clone does.
--
Philip
next prev parent reply other threads:[~2015-05-21 19:45 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 [this message]
2015-05-22 6:37 ` Johannes Schindelin
2015-05-22 6:49 ` Jeff King
2015-05-24 19:07 ` Junio C Hamano
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=3516DC60279A42188EE2AA394921FC70@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.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.
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).