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

Issue 611381 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
cwallez@chromium.org
tandrii@chromium.org
█ andyb...@chromium.org
jmad...@chromium.org
rmis...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Gerrit allows you to CQ+2 on non-top-level patch sets

Project Member Reported by jmad...@chromium.org, May 12 2016 
Not sure if this is the right place to report this, but see https://chromium-review.googlesource.com/#/c/343994/. Here accidentally a developer put +2 CQ on Patch Set 1, when the latest was patch set 2. Then the CQ did nothing. It would be ideal if we could only mark CQ bits on the latest patch set.

Andrii maybe you can find the right home for this issue.

Comment 1 by tandrii@chromium.org, May 12 2016

Cc: tandrii@chromium.org andyb...@chromium.org
Owner: ----
Status: Available (was: Assigned)
This is KI. I don't know how to disable voting on older patches, but i agree that it'd be a good thing.

Comment 2 by andyb...@chromium.org, May 12 2016 

The current GWT UI disables the ability to set labels on patch sets if it knows there’s a newer one. Maybe that’s a better solution.

Comment 3 by tandrii@chromium.org, May 12 2016 

Oh, actually yes, that is a better solution.

Comment 4 by andyb...@chromium.org, May 13 2016

Status: WontFix (was: Available)
WillFix :). Just moving to Gerrit issue tracker — https://code.google.com/p/gerrit/issues/detail?id=4114
►

Sign in to add a comment