<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 25, 2011, at 6:18 PM, Jesus Cea wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On 12/11/11 16:56, Éric Araujo wrote:<br><blockquote type="cite">Ezio and I chatted a bit about his on IRC and he may try to write<br></blockquote><blockquote type="cite">a Python parser for Misc/NEWS in order to write a fully automated<br></blockquote><blockquote type="cite">merge tool.<br></blockquote><br>Anything new in this front? :-)</span></blockquote></div><br><div>To me, it would make more sense to split the file into a Misc/NEWS3.2 and Misc/NEWS3.3 much as we've done with whatsnew. That would make merging a piece of cake and would avoid adding a parser (an its idiosyncracies) to the toolchain.</div><div><br></div><div><br></div><div>Raymond</div></body></html>