On 04/28/2015 10:55 PM, Shyam wrote:
On 04/28/2015 01:10 PM, Niels de Vos wrote:
On Tue, Apr 28, 2015 at 05:56:56PM +0100, Justin Clift wrote:
This sounds like it might be useful for us:
https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/config-labels.html#label_copyAllScoresOnTrivialRebase
label.Label-Name.copyAllScoresOnTrivialRebase
If true, all scores for the label are copied forward when a new patch
set is uploaded that is a trivial rebase. A new patch set is considered
as trivial rebase if the commit message is the same as in the previous
patch set and if it has the same code delta as the previous patch set.
This is the case if the change was rebased onto a different parent. This
can be used to enable sticky approvals, reducing turn-around for trivial
rebases prior to submitting a change. Defaults to false.
Yes/no/?
Yes for me.
Yes ++ (if above is true ;) )
Recollect seeing similar behavior in openstack CI infrastructure. Should
be good to flip it on.
-Vijay
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
