From: Rene Herman <rene.herman@gmail.com>
Date: Tue, 17 Apr 2007 16:10:55 GMT
Subject: Re: git branch --switch?
Message-ID: <4624F18F.6070906@gmail.com>
In-Reply-To: <8c5c35580704170855ke426d86vac6e9b3b67fea5ea@mail.gmail.com>

On 04/17/2007 05:55 PM, Lars Hjemli wrote:

> On 4/17/07, Rene Herman <rene.herman@gmail.com> wrote:

>> git clone -l -s -n <a local linux repo> local
>> git checkout -b v20 v2.6.20
>> git branch a
>> git branch b
>> git branch c
>>
>> Step 1, 3, 4 and 5 of this are nearly instantaneous but 2 isn't
> 
> I might have misunderstood your goal, but have you tried
> 
> git clone -l -s -n <a local linux repo> local
> git branch a v2.6.20
> git branch b a
> git branch c a
> 
> Now a, b and c all point at v2.6.20, while HEAD points as master.

Well, yes, they do, and I could also do

git branch b v2.6.20
git branch c v2.6.20

directly then (right?) but I do want that "v20" branch in the middle. The 
cloned repo is a linus repo, and that v20 is where I'll be pulling 2.6.20.y 
updates into; a merge branch will then merge v20, a, b and c into what I 
will be compiling.

As said, given that I need to checkout things anyway to do something with 
them it'a all not essential but as a newbie, I just thought that a "branch 
--and-set-as-current new_branch" made sense. My sense of sense may be crap; 
I've largely avoided dealing with souce code management, regarding CVS and 
SVN as unfortunate facts of life to work around and forget, mostly.

Rene.