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