New issue
Advanced search Search tips

Issue 855130 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
jgruber@chromium.org
cbruni@chromium.org
szuend@google.com
rmis...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Previous locations:
gerrit:9329


Sign in to add a comment

Reland: should succeed despite merge conflicts

Project Member Reported by jgruber@chromium.org, Jun 21 2018 
Currently, when a Reland has merge conflicts with master, one needs to fall back to the manual process of rebasing locally and creating a new CL. The connection between the original CL and the reland is lost.

Would it be possible to create a reland CL even in the presence of merge conflicts? It'd be fine if the CL does not compile/apply cleanly, as long as a reland gerrit CL is created.

Comment 1 by kaspern@google.com, Jun 21 2018

Project: chromium
Moved issue gerrit:9329 to now be issue chromium:855130.

Comment 2 by jgruber@chromium.org, Jun 25 2018

Cc: cbruni@chromium.org
Owner: kaspern@google.com
Status: Assigned (was: New)
Why was this moved to chromium? It seems like this issue will be totally lost here, esp. since there's no component assigned and no owner. 

(Same as https://crbug.com/855131)

Comment 3 by kaspern@google.com, Jun 25 2018

Components: Infra>Codereview>Gerrit
Labels: -Priority-3
Owner: aga...@chromium.org
Reland functionality is not native to Gerrit, and is provided by a plugin. 

I was expecting this bug to go through a normal Chromium triage process of some sort -- here's my best guess for triage.

Comment 4 by aga...@chromium.org, Aug 10

Labels: Pri-2
Owner: ----
Status: Available (was: Assigned)
Triaging, but unassigning from myself as I'm on sabbatical.
►

Sign in to add a comment