Re: [PATCH] add --remote option to git-clone.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 2, 2007, 10:48 UTC
Message-ID: <Pine.LNX.4.63.0702021146440.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <7vmz3xmju9.fsf@assigned-by-dhcp.cox.net>

Hi,

On Thu, 1 Feb 2007, Junio C Hamano wrote:

Show 19 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Fri, 2 Feb 2007, Michael S. Tsirkin wrote:
> > ...
> >> One can always get more branches later, is my approach.
> >
> > Yes. But in the same vein, one can add _one_ branch to an empty repo 
> > either. So, with your reasoning, your patch wouldn't be needed to begin 
> > with.
> 
> Indeed.
> 
> > But I find it useful. Even the version where you are not limited to one 
> > branch.
> 
> I am not against the general idea of tracking a subset of
> branches, but issues include:
>
> [explains why git-remote is a better place for this]

Seeing your patch to git-remote, it feels more natural, too. Especially since that (or which? :-D) does not give the term "clone" a Microsoft'esque completely new meaning.

Ciao, Dscho