You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ba83229a73
Currently, the "--upstream A" option for new-branch behaves totally different than "--upstream_current". While "--upstream A" checks out branch A and then creates a new branch which tracks A, "--upstream_current" creates a new branch for the current HEAD and sets the upstream to the previously checked out branch. As the documentation does not mention that any of the options changes the currently-checked-out commit (HEAD), this CL changes the semantics of "git new-branch --upstream A B" to be identical to "git checkout -b B && git branch --set-upstream-to A". It also slightly extends the documentation to mention that in any case the new branch is based on HEAD. R=iannucci@chromium.org Change-Id: Ic335d2caf27cb6afca1b8bc5a008424c0e880fca Reviewed-on: https://chromium-review.googlesource.com/c/1350748 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Auto-Submit: Clemens Hammacher <clemensh@chromium.org> |
7 years ago | |
|---|---|---|
| .. | ||
| git-cl.1 | ||
| git-drover.1 | ||
| git-footers.1 | ||
| git-freeze.1 | ||
| git-hyper-blame.1 | ||
| git-map-branches.1 | ||
| git-map.1 | ||
| git-mark-merge-base.1 | ||
| git-nav-downstream.1 | ||
| git-nav-upstream.1 | ||
| git-new-branch.1 | 7 years ago | |
| git-rebase-update.1 | ||
| git-rename-branch.1 | ||
| git-reparent-branch.1 | ||
| git-retry.1 | ||
| git-squash-branch.1 | ||
| git-thaw.1 | ||
| git-upstream-diff.1 | ||