Hi Charles,<br><br>sorry for this overdue answer!<br><br><div class="gmail_quote">2009/10/8 Charles Lepple<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Oct 8, 2009, at 4:13 AM, Arjen de Korte wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Citeren Charles Lepple<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Another lesson from testing the merge into the trunk: the ChangeLog<br>
file will be a mess (since both the trunk and the branch have changes<br>
adjacent to each other, most of the revisions conflict with the<br>
previous revision). We might want to consider generating the ChangeLog<br>
file from the SVN revision messages.<br>
</blockquote>
<br>
Considering the latter, I'm all for it. Most of the time, the SVN revision message is duplicated from the ChangeLog anyway (at least, that's what I do). We might just as well automate this, so we only need to fill in the SVN revision message.<br>
</blockquote>
<br></div>
And with something like this, we might even be able to match the current ChangeLog format:<br>
<br>
<a href="http://arthurdejong.org/svn2cl/" target="_blank">http://arthurdejong.org/svn2cl/</a><br>
<br>
I think I've seen one or two more variants of this - I will dig them up if that's what we want to do.</blockquote></div><br>excellent! I'm very happy to see you back on this subject.<br>I'd be pleased to see it in action...<br>
<br>now for the doc plans (from you original message), there's no hurry for a merge.<br>even more now that the ChangeLog point will be addressed.<br>so the plan is to continue the conversion, until we reach something complete enough to go on a beta round.<br>
<br>on my side, I've just started to commit a bunch of User Manual updates.<br>
I've planned to get back on the website soon so that we can publish it on new.n.o and go on a beta round. The last points being the driver.list evolution (I should send another mail tonight on this), the protocols library (first pass) and obviously the layout / usability issues we've talked about before.<br>
<br>I still also have to take a deeper look at the manpages (big thanks for your work here).<br><br>cheers,<br>
Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops" target="_blank">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br>