<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Chris,<div><br></div><div>I see your point now. We are not using gerrit with a way it was designed for (when +2 should be there to submit; seems our gatekeepers doing +2).</div><div>You are right it is impossible to build search for gatekeeper from plain gerrit without it modification.</div><div><br></div><div>There are still some ways to workaround that:</div><div>* <a href="http://en.wikibooks.org/wiki/Git/Gerrit_Code_Review">http://en.wikibooks.org/wiki/Git/Gerrit_Code_Review</a> (A hook could - for instance - allow a project to install an automated gatekeeper to vote +2 'submit approved' when sufficient +1 votes 'looks good to me' have been received)</div><div>* <a href="http://review.whamcloud.com/Documentation/prolog-cookbook.html#_example_12_1_1_2_code_review">http://review.whamcloud.com/Documentation/prolog-cookbook.html#_example_12_1_1_2_code_review</a> (but I don't know if it will get right searches..)</div><div>* in Xyratex we are using Jira state "Landing" to build filter for gatekeeper.</div><div><br></div><div>OK, even if we could't separate gatekeeper changes from other, filter is still useful to check issues with no feedback for a long time.</div><div><br><div>
<div><div>Thanks,</div><div>Denis</div></div>
</div>
<br></div></body></html>
<br>
<pre style="white-space:pre-wrap;color:rgb(34,34,34);background-color:rgb(255,255,255)"><hr>For additional information including the registered office and the treatment of Xyratex confidential information please visit <font color="#1155cc"><a href="http://www.xyratex.com/" target="_blank">www.xyratex.com</a></font>
</pre><div><hr></div>