Re: Update local tracking refs when pushing- no way to disable

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi,

On Thu, 5 Jul 2007, Daniel Barkalow wrote:

> What git-fetch and git-push care about is whether you have an entry 
> "remote.<name>.fetch" with a colon and stuff on the right of it. If so, 
> this is a pattern that is used to generate the duplicate branch heads 
> that you don't want. git clone sets it up to a default pattern 
> (refs/remotes/origin/*), and I don't think there's any way to make it 
> not do that, but you can just reconfigure it afterwards if you don't 
> like it.

Related, but not identical, is the problem illustrated in 
http://thread.gmane.org/gmane.comp.version-control.git/49888

IMHO there is a bug. IIUC git push first looks for common ref names on the 
local and remote side (yes, refs/remotes are excluded since v1.5.3-rc0~9, 
but the underlying problem is still there). Then it pushes them. But here, 
something seems to have gone wrong: refs/remotes/origin/HEAD is a symref. 
And the corresponding ref is updated. Should git-push not just _not_ 
update symrefs?

Ciao,
Dscho