Skip to content

C
Chromium_Depot_tools
Switch branch/tag
  1. 15 Mar, 2019 1 commit
  3. 22 Feb, 2019 2 commits
  5. 20 Feb, 2019 1 commit
  7. 04 Feb, 2019 1 commit
  9. 31 Jan, 2019 1 commit
  11. 11 Jan, 2019 2 commits
  13. 09 Jan, 2019 1 commit
  15. 18 Dec, 2018 1 commit
  17. 17 Dec, 2018 2 commits
  19. 13 Dec, 2018 1 commit
  21. 05 Dec, 2018 2 commits
    • Clemens Hammacher's avatar
      Revert "Fix semantics of git new-branch --upstream" · 19238fc3
      Clemens Hammacher authored 
      This reverts commit ba83229a.

Reason for revert: After mail discussion we came to the conclusion that the old behavior makes more sense.

Original change's description:
> Fix semantics of git new-branch --upstream
> 
> 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>

TBR=iannucci@chromium.org,tandrii@chromium.org,clemensh@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Change-Id: I7463935af172f0801c7da94d2de106a02fc4c42e
Reviewed-on: https://chromium-review.googlesource.com/c/1362972Reviewed-by: 's avatarSergiy Belozorov <sergiyb@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      19238fc3
    • Edward Lemur's avatar
      git-cl: Set Code-Review label as a git push argument. · 687ca907
      Edward Lemur authored 
      Bug: 877717
Change-Id: I6541a971068aae662b086eba84448bd0769f1a09
Reviewed-on: https://chromium-review.googlesource.com/c/1362405Reviewed-by: 's avatarAndrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: 's avatarEdward Lesmes <ehmaldonado@chromium.org>
Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org>
      687ca907
  23. 04 Dec, 2018 1 commit
    • 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
  25. 01 Dec, 2018 1 commit
  27. 30 Nov, 2018 1 commit
  29. 26 Nov, 2018 1 commit
  31. 21 Nov, 2018 2 commits
  33. 19 Nov, 2018 2 commits
  35. 16 Nov, 2018 2 commits
  37. 03 Nov, 2018 1 commit
  39. 01 Nov, 2018 2 commits
  41. 31 Oct, 2018 1 commit
  43. 30 Oct, 2018 3 commits
  45. 23 Oct, 2018 1 commit
  47. 22 Oct, 2018 1 commit
  49. 18 Oct, 2018 1 commit
  51. 16 Oct, 2018 4 commits
  53. 15 Oct, 2018 1 commit