From: "Jurko Gospodnetić" <jurko.gospodnetic@docte.hr>
To: git@vger.kernel.org
Subject: Branch renaming not updating the configuration correctly.
Date: Mon, 28 Jul 2008 15:36:09 +0200 [thread overview]
Message-ID: <g6ki09$81c$1@ger.gmane.org> (raw)
Hi.
I noticed that the .git/config file is not updated completely in case
you create two branches aaa and bbb, set the repository up so it
automatically merges changes from bbb into aaa and then rename the branches:
Here is an exact list of commands and config file contents
illustrating the problem:
> git branch aaa
> git branch bbb
> git config --add branch.aaa.remote .
> git config --add branch.aaa.merge bbb
-- .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'.
Hope this helps.
Best regards,
Jurko Gospodnetić
next reply other threads:[~2008-07-28 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:36 Jurko Gospodnetić [this message]
2008-07-28 13:49 ` Branch renaming not updating the configuration correctly Johannes Schindelin
2008-07-28 14:06 ` Jurko Gospodnetić
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g6ki09$81c$1@ger.gmane.org' \
--to=jurko.gospodnetic@docte.hr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).