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 10:33:41 +0000 (UTC) [thread overview]
Message-ID: <slrnhhcgi8.cpv.sn_@experimentalworks.net> (raw)
In-Reply-To: 20091202192028.6117@nanako3.lavabit.com
On 2009-12-02, Nanako Shiraishi <nanako3@lavabit•com> wrote:
> Quoting David Soria Parra <sn_@gmx•net> writes:
>
>> I'm aware that it's not possible to give more than one --track
>> option. Implementing the possibility to specify multiple --track option
>> would certainly a good improvment later, but would also require a lot
>> more work as far as I understand the clone code.
>
> I'm sorry if I'm asking the obvious, but how can multiple --track
> options be a useful future enhancement? If I understand your use
> case correctly, it's useful when you want to work on only one
> branch that isn't the default, and that is why you don't want to
> get data necessary for other branches. What does it mean to give
> two --track options? You will get one master branch that tracks
> both versions, and "git pull" will merge both branches you track?
Similar to git remote add --track it'll pull all branches specified by a --track
option and checkout the first one or -o <name> if given. For me personally it's
not an improvemen, because I just need to clone on branch, but as git remote add allows
multiple branches specified by --track I thought this might be an improvment.
next prev parent reply other threads:[~2009-12-02 10:34 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 [this message]
2009-12-02 19:08 ` Jeff King
2009-12-02 19:27 ` David Soria Parra
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=slrnhhcgi8.cpv.sn_@experimentalworks.net \
--to=sn_@gmx$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox