New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 652651 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

git cl upload --gerrit does not work when tracking a branch uploaded to Rietveld

Project Member Reported by rmis...@google.com, Oct 4 2016

Issue description

1. Make changes to some files
2. git add, then git commit them
3. Use git cl upload --gerrit
4. Observe that you get the following error message:
        Upload upstream branch <branch> first.
        Note: maybe you've uploaded it with --no-squash.
              If so, then re-upload it with: git cl upload --squash

Doing this without --gerrit seems to work fine. --no-squash does not help either.


 

Comment 1 by rmis...@google.com, Oct 4 2016

Project: chromium
Copied  issue chromium:652651  from  issue skia:5817 

Comment 2 by rmis...@google.com, Oct 4 2016

Cc: raftias@google.com msarett@chromium.org tandrii@chromium.org
Labels: -Type-Defect -Priority-Medium Milestone-Dogfood Proj-Gerrit-Migration Pri-2 Type-Bug-Regression
Status: avfa
I intend to do this for Dogfood milestone. If you think it has to be earlier for Skia, bump up to Milestone-Fishfood please.
Status: Available (was: avfa)
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 4 2016

Labels: Hotlist-Google

Comment 6 by aga...@chromium.org, Nov 30 2016

Status: WontFix (was: Available)
Summary: git cl upload --gerrit does not work when tracking a branch uploaded to Rietveld (was: git cl upload --gerrit does not seem to work as expected)
I honestly don't think we need to support this. Supporting uploading CLs to different systems from a single repo is enough; we shouldn't need to support uploading different CLs in the same tracking chain.

Sign in to add a comment