git cl uses different upstream than git |
|||||
Issue descriptionrepro steps fetch pdfium cd pdfium git checkout origin/chromium/2743 git checkout -b merge git cl upstream expected results: refs/remotes/origin/chromium/2743 actual results: refs/remotes/origin/master
,
Aug 3 2016
,
Aug 17 2016
,
Aug 18 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 28 2017
This is because git-cl expects you to have tracking information set up. Without tracking information, it can't tell which branch you want to have set up.
Following your steps, running "git show @{u}" (to get git's idea of what the upstream is) also doesn't work. There isn't an upstream branch, because when you run "git checkout origin/chromium/2734", you end up in a detached-head state.
The right thing to do is "git checkout -t origin/chromium/2743 -b merge". Then both "git show @{u}" and "git cl upstream" will work.
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tandrii@chromium.org
, Jul 21 2016Status: Available (was: Untriaged)