From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
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: Wed, 27 May 2015 04:19:10 -0400 [thread overview]
Message-ID: <20150527081909.GA10008@peff.net> (raw)
In-Reply-To: <xmqqtwv1bxpy.fsf@gitster.dls.corp.google.com>
On Sun, May 24, 2015 at 12:07:53PM -0700, Junio C Hamano wrote:
> 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.
In the meantime, do you want to pick up patches 1 and 2? I think they
are cleanups that stand on their own, whether we do patch 3 or not.
-Peff
next prev parent reply other threads:[~2015-05-27 8:19 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 [this message]
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=20150527081909.GA10008@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 \
--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).