<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 28, 2011, at 5:35 PM, Chandler Carruth wrote:</div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">Thanks for working on the Clang release notes, they're looking great. I still think it makes sense to have a high level summary of what is new in Clang in the llvm release notes, but maybe some of the bullets can be [re]moved.</blockquote>
<div><br></div><div>Yea, that was all I was thinking. I definitely agree that a summary is important.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Do we have a plan for how to get the release notes links finalized?</blockquote><div><br></div><div>Not really... My only idea off the cuff would be to modify them (both) on the branch. There are links in both directions. Other ideas? I'll think about cleaner solutions...</div>
</div>
</blockquote></div><br><div>I don't really know of a cleaner solution here: we don't currently unpack the Clang doc's in the release directory. Maybe we should start doing this in 3.1, but a simple hack is probably fine for LLVM 3.0. Please synch up with Bill about this specifically.</div><div><br></div><div>-Chris</div></body></html>