I was reading:<br><a href="http://bazaar-vcs.org/BzrVsGit#head-5dd8613f1f333ead9dbb6acea70cd6ccedb7ea64">http://bazaar-vcs.org/BzrVsGit#head-5dd8613f1f333ead9dbb6acea70cd6ccedb7ea64</a><br><br>and found a link to a long svn mail by Karl Fogel (who is helping out here now too AIUI):<br>
<a href="http://svn.haxx.se/dev/archive-2007-06/0780.shtml">http://svn.haxx.se/dev/archive-2007-06/0780.shtml</a><br>==<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Those of us who work in version control, who think about branching and
<br>
merging and change algebra and diff3/diff4 algorithms all day, often
<br>
forget this. One of Subversion's biggest advantages, and one of the
<br>
reasons it's taking over the world, is that it's really easy to
<br>
understand. There's a repository; you check stuff out; you modify the
<br>
stuff; you check it back in. Comprehensibility is a big part of
<br>
survivability: wherever Subversion goes from here, it must not become
<br>
so complex that it can't be explained in five minutes or less with no
<br>
questions from the audience. (I've witnessed enough explanations of
<br>
decentralized systems to know that their learning curve is generally a
<br>
bit steeper, though it may well be worth it.)
</blockquote><div>==<br><br>This made me think of something somebody at work asked me recently:<br>"I need to backport this fix to an older release branch, but I don't want to think about it. Can you quickly do it for me?"<br>
<br>Granted it is not the simplest of scenarios, and our setup is also suboptimal (even unoptimal :) . <br>(several developers sharing the same workingtrees on a dev server, <br>because the setup for the whole system is so complicated it was deemed better to just <br>
set up one instance and we share it)<br><br>Anyways, I can see that a lot of deverlopers think that bzr is complicated.<br>Maybe because as Karl says we are doing complicated things.<br><br>The sad thing now is that the powers that be, will probably decide that we<br>
have to standardise on svn now (for this and other reasons). That would just break my heart.<br>Don't worry, I won't go down without a fight (among others blaming our setup).<br>It might sound stupid that one might consider resigning over a version control system,<br>
but bzr has grown so much a part of my lifestyle, that I can't imagine living without it.<br>Ah well if it does happen, I assume bzr-svn is going to get a workout from me, <br>expect patches :)<br></div><br>So I hope you guys are inspired to help out Karl in doing better PR and user-friendlier UI's/GUI's for bzr,<br>
it could save someone's life! <br><br>-- <br><| regards<br>U| Marius<br>H| <>< <br>Z| <a href="http://amanica.blogspot.com/">http://amanica.blogspot.com/</a><br><| <br>E| <a href="http://bazaar-vcs.org/">http://bazaar-vcs.org/</a><br>
<| because I don't trust version control systems with less than 14777 unit tests<br>