<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><blockquote type="cite"><div>On Jul 9, 2014, at 4:15 PM, Ryosuke Niwa <<a href="mailto:rniwa@webkit.org">rniwa@webkit.org</a>> wrote:</div><div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> Again, im not requesting anything new here. The consensus on webkit-dev has been to ping the author/reviewer on IRC or via email and comment in the original bug PRIOR to using webkitbot to start reverting the patch.</div></div></blockquote><div><br></div><div>I went through the first handful of emails on that thread. The original request that wasn’t meeting a lot of opposition before I stopped digging through the thread was:</div><div>“Please contact the author/reviewer and give them a reasonable amount of time <b>before rolling out their patch</b>.”</div><div><br></div><div>I did not reach the message where the consensus was “contact the author and reviewer manually, <b>do not use webkitbot</b>”</div><div><br></div><div>I believe that using webkitbot:</div><div>1 - Comments in a new bugzilla created specifically because there’s an issue</div><div>2 - Comments in the original bugzilla notifying of an issue</div><div>3 - Emails the author and reviewer by virtue of CC’ing them on the bugzilla(s)</div><div>4 - Does *not* roll out the patch.</div><div><br></div><div>Assuming my webkitbot command contains a description of the reason this patch is suspect, including a URL to the failure, can you further explain why using webkitbot is unreasonable?</div><div><br></div><div>Maybe that reasoning was reached in the thread you linked to and I didn’t find it yet. I would appreciate it being restated here as the project has progressed quite a bit since Dec 2012.</div><div><br></div><div>Thanks,</div><div>~Brady</div></div><br></body></html>