<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;">On Jan 6, 2014, at 3:16 PM, Eric Christopher <<a href="mailto:echristo@gmail.com">echristo@gmail.com</a>> wrote:<div><blockquote type="cite">It's not what we've been doing for the last few years but if you're cool with it then…<br></blockquote><div><br></div><div>Clearly if there are major structural problems with a patch, it isn’t appropriate, but a very common scenario is:</div><div><br></div><div>person a) "here’s a patch”</div><div>person b) “looks good, here are a bunch of little things to fix”</div><div>person a) “done and committed!”</div><div>person b) “woot”</div><div><br></div><div>If the feedback wasn’t incorporated right, the last line would be replaced with “wait, you need to do this too!” and if atrocious crimes are committed, then the patch gets reverted. This is pretty standard with post-commit review.</div><div><br></div><div>-Chris</div><div><br></div><br><br><br><blockquote type="cite"><div>On Mon Jan 06 2014 at 3:15:54 PM, Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Jan 6, 2014, at 2:55 PM, Eric Christopher <<a href="mailto:echristo@gmail.com" target="_blank">echristo@gmail.com</a>> wrote:<br>
> You should wait for an explicit ack on committing a patch if it's in review. It's a bit anti-social to do so otherwise and that people are waiting isn't a good enough reason to skip that.<br>
<br>
It is pretty common to commit after addressing a list of comments. Continuously iterating on patches over the span of weeks isn’t the normal practice.<br>
<br>
-Chris<br>
<br>
</blockquote>
</blockquote></div><br></body></html>