Re: push.default???

From: Andreas Ericsson <ae@op5.se>
Date: Jun 23, 2009, 13:21 UTC
Message-ID: <4A40D6C2.2060700@op5.se>
In-Reply-To: <20090623131131.GA7011@pvv.org>

Finn Arne Gangstad wrote:

Show 17 quoted lines

> On Tue, Jun 23, 2009 at 02:59:10PM +0200, Paolo Bonzini wrote:
> [...]
>> Before going on, can you explain your use case for --push=tracking (in a  
>> case where --push=current wouldn't do the same)?
> 
> The idea with "tracking" is to push the current branch to wherever it
> would pull from, making push & pull "equivalent" in some sense.
> 
> This is different from "current" if you have/choose to name the local
> branch something else than the remote branch. This happens a lot when
> using multiple remotes.
> 
> E.g. some remotes have only a single active branch called "master",
> and you have to name it something else locally, or several people have
> local branches called "beta", and you have to name it something like
> "fred-beta" locally if you are working on fred's beta.
>

Umm. Why not name it after the feature you're working on instead of the branch you started from? That way, you get fred/beta (assuming you've added Fred's repo as a remote named "fred" ofcourse) and all your branches have names that never (in theory) clash with any of your upstreams.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.