From: chris <jugg@hotmail.com>
To: git@vger.kernel.org
Subject: checkout new branch tracks wrong remote (bug?)
Date: Wed, 30 Mar 2011 02:27:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20110330T040437-823@post.gmane.org> (raw)
I have two remotes configured.
One is "origin" which has a local tracking branch "master" for "origin/master".
The other is "mirror" which has option mirror = true
While on the local branch master, I issue the command:
$ git checkout -b wip
The branch "wip" is created and oddly configured to track the "mirror" remote.
Here is the .git/config after the "wip" branch was created:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ssh://myserver.com/srv/git/myproject.git
[branch "master"]
remote = origin
merge = refs/heads/master
[remote "mirror"]
url = ssh://chris@myserver.com/srv/git/mirrors/chris/myproject.git
fetch = +refs/*:refs/*
mirror = true
[branch "wip"]
remote = mirror
merge = refs/heads/master
$ git --version
git version 1.7.4.1
$ git config branch.autosetupmerge
$
I do not expect this "wip" branch to be tracking the "mirror" remote, but rather
"origin", according to the documentation.
chris
next reply other threads:[~2011-03-30 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 2:27 chris [this message]
2011-03-30 14:59 ` checkout new branch tracks wrong remote (bug?) Jeff King
2011-03-30 19:51 ` [PATCH 0/3] better "remote add --mirror" semantics Jeff King
2011-03-30 19:52 ` [PATCH 1/3] remote: disallow some nonsensical option combinations Jeff King
2011-03-30 19:53 ` [PATCH 2/3] remote: separate the concept of push and fetch mirrors Jeff King
2011-03-30 20:45 ` Junio C Hamano
2011-03-30 20:57 ` Jeff King
2011-03-30 22:22 ` Junio C Hamano
2011-03-31 2:44 ` chris
2011-03-31 2:50 ` chris
2011-03-31 4:03 ` Junio C Hamano
2011-03-31 12:59 ` chris
2011-03-30 19:53 ` [PATCH 3/3] remote: deprecate --mirror Jeff King
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=loom.20110330T040437-823@post.gmane.org \
--to=jugg@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.