<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><div>On Jul 1, 2014, at 12:44 PM, Chandler Carruth <<a href="mailto:chandlerc@gmail.com">chandlerc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 12:01 PM, Zachary Turner <span dir="ltr"><<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Additionally, I frequently see patches going in without review. What is LLDB's policy on this?</blockquote><div><br>
</div><div>FWIW, I would assume (from the discussions with Chris when LLDB first joined the LLVM projects) that it has the same policy as LLVM here. Chris, I don't actually see any clarification about this on the LLDB website, could we get that in there? I'm somewhat concerned that there is essentially *no* developer policy posted for LLDB.</div>
<div><br></div></div></div></div></blockquote><br></div><div>Aside from the coding standards being substantially different (which I’m not thrilled about), LLDB follows the same developer policies as the rest of LLVM.</div><div><br></div><div>-Chris</div><br></body></html>