zarb-ml/mageia-dev/attachments/20120314/2982b752/attachment.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

<br><br><div class="gmail_quote">2012/3/14 Thierry Vignaud <span dir="ltr">&lt;<a href="mailto:thierry.vignaud@gmail.com">thierry.vignaud@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 14 March 2012 13:40,  &lt;<a href="mailto:root@mageia.org">root@mageia.org</a>&gt; wrote:<br>
&gt; Revision 3455 Author ennael Date 2012-03-14 13:40:46 +0100 (Wed, 14 Mar<br>
&gt; 2012)<br>
&gt;<br>
&gt; Log Message<br>
&gt;<br>
&gt; update changelog<br>
<br>
</div>As you can see in the commit diff, svn2cl is buggy, has been buggy for years,<br>
and repeat some entries (I looked at it some years ago, I think it was due to<br>
different TZ between client &amp; server)<br></blockquote><div><br></div><div>Indeed...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe should we just write important stuff in a NEWS file and just use svn log<br>
for the full log.<br></blockquote><div><br></div><div>yep that would also help to have same kind of process for all mageia specific soft</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

If you fear a server crash, you can use git svn and you&#39;ve a full compact<br>
local backup<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br>