• Clemens Hammacher's avatar
    Fix semantics of git new-branch --upstream · ba83229a
    Clemens Hammacher authored
    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/1350748Reviewed-by: 's avatarRobbie Iannucci <iannucci@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Auto-Submit: Clemens Hammacher <clemensh@chromium.org>
    ba83229a
Name
Last commit
Last update
..
git-cl.1 Loading commit data...
git-drover.1 Loading commit data...
git-footers.1 Loading commit data...
git-freeze.1 Loading commit data...
git-hyper-blame.1 Loading commit data...
git-map-branches.1 Loading commit data...
git-map.1 Loading commit data...
git-mark-merge-base.1 Loading commit data...
git-nav-downstream.1 Loading commit data...
git-nav-upstream.1 Loading commit data...
git-new-branch.1 Loading commit data...
git-rebase-update.1 Loading commit data...
git-rename-branch.1 Loading commit data...
git-reparent-branch.1 Loading commit data...
git-retry.1 Loading commit data...
git-squash-branch.1 Loading commit data...
git-thaw.1 Loading commit data...
git-upstream-diff.1 Loading commit data...