From: Jeff King <peff@peff.net>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
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: Fri, 22 May 2015 02:50:22 -0400 [thread overview]
Message-ID: <20150522065022.GB27716@peff.net> (raw)
In-Reply-To: <8895881cd3f324d2b8a827e311296a48@www.dscho.org>
On Thu, May 21, 2015 at 06:05:31PM +0200, Johannes Schindelin wrote:
> > +--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.
Yeah, I agree that is much better (it's the "4/3" I suggested in the
cover letter).
-Peff
next prev parent reply other threads:[~2015-05-22 6:50 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
2015-05-27 8:19 ` Jeff King
2015-05-27 19:35 ` Junio C Hamano
2015-05-22 6:50 ` Jeff King [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150522065022.GB27716@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=mhagger@alum.mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.