From: David Soria Parra <sn_@gmx.net>
To: git@vger.kernel.org
Subject: Re: [PATCH v2] Add --track option to git clone
Date: Wed, 2 Dec 2009 19:27:27 +0000 (UTC) [thread overview]
Message-ID: <slrnhhdfr1.d2h.sn_@experimentalworks.net> (raw)
In-Reply-To: 20091202190807.GB30778@coredump.intra.peff.net
On 2009-12-02, Jeff King <peff@peff.net> wrote:
> 1. Add "--track foo" as a convenience wrapper for "-f foo -b foo".
>
> 2. If no "-b" is given, the first "-f" is assumed as "-b". So "git
> clone -f foo" becomes equivalent to David's --track.
>
> And of course the name "-f" (for --fetch, if you were wondering) is open
> to suggestion.
>
> What do you think?
>
This approach is much better than my initial proposal. Sadly I won't have time
to implement this, which is why I wrote the simplest working solution for me.
Fetch seems to reasonable. I can rewrite the patch to be able to use refspecs, but
it would require additional refactoring to be able to specify multiple --fetch parameters.
David
next prev parent reply other threads:[~2009-12-02 19:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 22:51 [PATCH v2] Add --track option to git clone David Soria Parra
2009-12-01 22:51 ` [PATCH v2 1/2] Teach clone to clone just one remote branch using --track David Soria Parra
2009-12-01 22:51 ` [PATCH v2 2/2] Documentation: Add --track option to the git clone manpage David Soria Parra
2009-12-02 2:08 ` [PATCH v2] Add --track option to git clone Sean Estabrooks
2009-12-02 7:20 ` David Soria Parra
2009-12-02 10:20 ` Nanako Shiraishi
2009-12-02 10:33 ` David Soria Parra
2009-12-02 19:08 ` Jeff King
2009-12-02 19:27 ` David Soria Parra [this message]
2009-12-02 21:07 ` Nanako Shiraishi
2009-12-02 22:37 ` Jeff King
2009-12-02 23:02 ` Junio C Hamano
2009-12-03 5:31 ` Björn Steinbrink
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=slrnhhdfr1.d2h.sn_@experimentalworks.net \
--to=sn_@gmx.net \
--cc=git@vger.kernel.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.
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.