Re: Branch renaming not updating the configuration correctly.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 28, 2008, 13:49 UTC
Message-ID: <alpine.DEB.1.00.0807281445340.8986@racer>
In-Reply-To: <g6ki09$81c$1@ger.gmane.org>

Hi,

On Mon, 28 Jul 2008, Jurko Gospodnetić wrote:

Show 17 quoted lines

> -- .git/config: --
> [branch "aaa"]
> 	remote = .
> 	merge = bbb
> ------------------
> 
>   > git branch -m aaa patched
>   > git branch -m bbb original
> 
> -- .git/config: --
> [branch "patched"]
> 	remote = .
> 	merge = bbb
> ------------------
> 
> And as you can see above, the branch.patched.merge configuration setting 
> did not get updated and still holds the old branch name 'bbb'.

I deem this not an "important" bug.

We usually do not set up tracking information for local branches, and I still do not know valid common scenarios for that workflow.

But hey, if it really bothers you, and you can come up with a non-intrusive patch (i.e. a patch that does not punish all users that do _not_ set up locally-tracking branches), I am sure it will be welcomed.

Ciao, Dscho