New issue
Advanced search Search tips

Issue 746982 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Can git cl patch force by default?

Project Member Reported by dsinclair@chromium.org, Jul 20 2017

Issue description

With the change to gerrit, every time I git cl patch I get the warning:

Committed patch for change 8390 patchset 1 locally.
Note: this created a local commit which does not have the same hash as the one uploaded for review. This will make uploading changes based on top of this branch difficult.
If you want to do that, use "git cl patch --force" instead.

I then delete the branch and redo it with --force. Is it possible to make the force happen automatically so we can easily work with the branches we're patching in?
 

Comment 1 by aga...@chromium.org, Jul 20 2017

Status: WontFix (was: Untriaged)
Unfortunately, no, at least not yet. I already tried that, and got thoroughly rebuffed by chromium-dev:
https://bugs.chromium.org/p/chromium/issues/detail?id=723787&desc=2#c14

Sign in to add a comment