<br><div class="gmail_quote">2010/10/27 Arjen de Korte<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Citeren Arnaud Quette<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
since we're using svn logs to generate the ChangeLog, I went on the server<br>
to modify this empty log msg with "Fix compilation warnings".<br>
</blockquote>
<br></div>
Yeah, I forgot to add a description here. Sorry about that...<br></blockquote><div><br>no problem. the only thing is that we have to take care of that since it's now used for the ChangeLog.<br>and we have to jump on the server to fix it too...<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
You may have noticed I'm in the process of fixing all compilation warnings I see on the openSUSE buildbot (which are quite a few). Most of the 'easy' ones are now fixed, the majority of the remaining ones require more attention.<br>
</blockquote><div><br>indeed, and that's perfectly in line with the final 2.6.0 round.<br>we are finalizing the AsciiDoc branch with Charles, and the merge should happen within a week.<br>do you have anything else in mind that needs to get into 2.6.0?<br>
<br>btw, once 2.6.0 is out, when you have a bit of time, I'd like to hear your thoughts on the static code checking ;-)<br><br>cheers,<br>Arnaud<br></div></div>