Re: git bug? + question

From: Sean <seanlkml@sympatico.ca>
Date: Nov 3, 2006, 21:24 UTC
Message-ID: <BAYC1-PASMTP01F45766D9195AAFD81789AEFE0@CEZ.ICE>
In-Reply-To: <20061103203610.GB7585@spearce.org>

On Fri, 3 Nov 2006 15:36:10 -0500 Shawn Pearce <spearce@spearce.org> wrote:

Show 15 quoted lines

> > Maybe even going as far as automatically creating a local branch
> > for each remote branch on clone is worth considering.
> 
> Nack.
> 
> I work with a workflow where our central repository has 2 important
> branches (vmtip and vmvt), and a bunch of transient developer
> topic branches (e.g. sp/foo).  We only have a master branch in this
> repository so that git-clone will clone it without choking during
> the clone.  Users tend to do immediately after a clone:
> 
> 	git branch -D master
> 	git branch -D origin
> 	git branch -D ... other topic branches not interested in ...
> 	edit .git/remotes/origin ... delete topic branches ...

I think your Nack was a little rash here. The feature would be quite useful to work flows other than yours. It sounds like what _you_ want is a feature to select branches when cloning rather than the current default of cloning all. That would stop your developers having to delete branches and editing .git/remotes/origin immediately after cloning.