0
我刚刚从1.8.4.3升级到1.9.1,并且我注意到更改后的行为。Git 1.9远程推送-u更改
在1.8.4.3当我想要git checkout -b new_branch
和git push -u origin new_branch
时,1.8.4.3会在名为origin
的远程中创建一个新的分支。
在1.9它只是说Branch git_1.9_test_branch set up to track remote branch master from origin by rebasing.
这是为什么?我怎么能1.9也创建类似于1.8的我的远程名为origin
的分支?如果我不这样做,当我git push
,我的变化被推到我分支的分支(在这种情况下master
),这显然是不受欢迎的。
一个下面的例子:
# 1.8.4.3
$ git checkout -b new_branch
Branch git_1.9_test_branch set up to track local branch master_newui by rebasing.
Switched to a new branch 'git_1.9_test_branch'
$ git push origin -u new_branch
Counting objects: 24, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.41 KiB | 0 bytes/s, done.
Total 6 (delta 3), reused 0 (delta 0)
To [email protected]:myorg/myrepo.com.git
* [new branch] new_branch -> new_branch
Branch new_branch set up to track remote branch new_branch from origin by rebasing.
# 1.9.1
$ git co -b new_branch
Branch new_branch set up to track local branch master_newui by rebasing.
Switched to a new branch 'new_branch'
$ git push -u origin new_branch
Branch new_branch set up to track remote branch master_newui from origin by rebasing.
Everything up-to-date
我的全球混帐配置有
[push]
default = upstream
的问题是不明确的。这就是1.9.x的工作原理。 – zerkms
@zerkms我已经用更多的说明更新了问题 - 问题是,当我'git push -u origin new_branch'没有在远程创建新的分支。所以,当我推送一个实际提交时,它最终被推送到我从(master)分支而不是'new_branch'分支的分支上。 – professormeowingtons
你的shell转储并没有反映你想知道的事情 - 当我读到这两个都告诉我一样。虽然1.9协议没有显示网络传输,但是这可能取决于控制台处理的变化。你有没有试图做出 - 推动? – florianb