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 07:20:44 +0000 (UTC) [thread overview]
Message-ID: <slrnhhc58g.cpv.sn_@experimentalworks.net> (raw)
In-Reply-To: BLU0-SMTP487572F057CC9D30C837D7AE950@phx.gbl
On 2009-12-02, Sean Estabrooks <seanlkml@sympatico•ca> wrote:
>> It tries to make the following usecase possible:
>> Imagine you are working on a project that has 1.x and a 2.x branch. The project
>> itself requires a complex setup (webserver, configuration files, etc). Setting up
>> 1.x and 2.x branch requires a lot of work, but a developer needs to maintain both.
>> He'll use the --track option to clone the 2.x branch into a directory and does the same
>> with the 1.x branch, where he setup the project. He can use locally separate repositories
>> while still being able to push to just one remote repository.
>
> This is already straightforward in Git without the limitation of tracking only
> a single remote branch. What is the necessity of doing this via the clone command?
>
> $ git init myrepo
> $ cd myrepo
> $ git remote add -t branch1.x -f origin <URL>
> $ git checkout -t origin/branch1.x
I'm aware that this is possible, but I want to have a shortcut for this as the users that I
helped with getting into git usually where confused about the point that you have to do it manually
via git init, so take the patch as a proposal to get more consistent interface for git clone.
david
next prev parent reply other threads:[~2009-12-02 7:21 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 [this message]
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
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=slrnhhc58g.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