<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; "><br><div><div>On Nov 19, 2013, at 11:01 AM, Bob Wilson <<a href="mailto:bob.wilson@apple.com">bob.wilson@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 19, 2013, at 10:58 AM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.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, Nov 19, 2013 at 10:48 AM, Bob Wilson <span dir="ltr"><<a href="mailto:bob.wilson@apple.com" target="_blank" class="cremed">bob.wilson@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3y5" style="overflow:hidden">I don't have a strong opinion on how we fix it, but I think it's really important to do something and get it done for the 3.4 release.<br>
</div></blockquote><div><br></div><div>I agree with everything here being a reasonable step for the 3.4 release except:</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":3y5" style="overflow:hidden">- implement Quentin's previous proposal for back-end diagnostics (and add a diagnostic handler to Apple's linker), so that we can warn about out-of-date debug info</div></blockquote>
</div><br>I don't think this is important for the release. I don't think open source people have any expectation of stability here, and while it is a nice-to-have, it doesn't seem necessary, and seems clearly like a significant extension that shouldn't be cherry-picked late into the release.</div>
</div>
</blockquote><br></div><div>OK, that's fair. As long as we can get it on trunk soon, we can cherry-pick it to an internal release branch.</div><br></div></blockquote></div><br><div>Two questions:</div><div><br></div><div>1) Can we reopen the bugzilla PR that I filed and use that to cover the additional of a version number and code to ignore the debug info when the version number does not match? Eric has already closed it twice, so I'm asking this time instead of just reopening it.</div><div><br></div><div>2) Who is going to do this work?</div></body></html>