Re: push.default???

From: Paolo Bonzini <paolo.bonzini@gmail.com>
Date: Jun 23, 2009, 13:28 UTC
Message-ID: <4A40D864.8040208@gmail.com>
In-Reply-To: <20090623131131.GA7011@pvv.org>

Finn Arne Gangstad wrote:

Show 11 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.

Yes, but when using multiple remotes is it really common that:

1) I have the permission to push to them (as opposed to sending a pull 
request)?  If I have permission to push only to the mob branch, for 
example, I would still set my tracking branch to the master branch.

2) I *do* want to push to them often?  If I use tracking for my topic 
branches, push.default=tracking seems a sure way to big mess when I do 
"git push" on the wrong branch.  Instead, with push.default=current "git 
push" would just tell me "new branch created" and then I can do "git 
push branch-name:" to delete the newly created branch.

I don't remember who it was, but when I tried changing the behavior for "git push" someone screamed loudly that fetching and pushing are two different things, and making things work uniformly across the two is not necessarily correct. The details probably were different, but I think that I am saying the same now.

Paolo