<div dir="ltr"><div>There are many ways to make server reliant software to be less server reliant.</div><div>But this is you, trying to implement a non-server-reliant software by hand.</div><div>IF you're coming to that, ... IMHO it is reinventing of the wheel.</div>
<div><br></div><div><br></div><div><div><br></div><div><br><div class="gmail_quote">On Thu, May 10, 2012 at 5:56 PM, Daniel Shahaf <span dir="ltr"><<a href="mailto:d.s@daniel.shahaf.name" target="_blank">d.s@daniel.shahaf.name</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nadav Har'El wrote on Thu, May 10, <a href="tel:2012" value="+9722012">2012</a> at 17:08:36 +0300:<br>
<div class="im">> * When you don't trust the server - and fear one day it will disappear<br>
> or even become malicious (trying to fake the content of the files or<br>
> their history), git is better because each person will have his own complete<br>
> copy of the history.<br>
<br>
</div>When you don't trust a server, and the server uses svn, you can keep an<br>
svnsync mirror of it at a location under your control.<br>
<br>
svnsync transfers new revisions as binary diffs against past revisions;<br>
past revisions are immutable.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Maxim Kovgan<br>
</div></div></div>