Comments on: synsync: another way to remotely backup / svnadmin dump an SVN repository http://kylecordes.com/2007/06/08/svnsync-svn-backup/ Kyle Cordes's Software Site Wed, 20 Aug 2008 09:02:14 +0000 http://wordpress.org/?v=2.0.11 by: Craig Buchek http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9960 Sat, 16 Jun 2007 17:20:46 +0000 http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9960 I've been hoping to attend a talk on this subject. ;) Jeff Barczewski had mentioned that he had also been looking at Bazaar and at least one of the others. Bazaar appears to be more well-maintained and well-documented than SVK, which is why I was considering it. I've been thinking for a while now that we should have an Advanced Programmers Group in town. I suppose the XP group (which I've never attended -- their meetings seem to be very infrequent) and the Ruby group are the closest we have. This topic would be great for a group like that. In the meantime, I guess I'll give SVK a try, and see if it works for me. I’ve been hoping to attend a talk on this subject. ;) Jeff Barczewski had mentioned that he had also been looking at Bazaar and at least one of the others. Bazaar appears to be more well-maintained and well-documented than SVK, which is why I was considering it.

I’ve been thinking for a while now that we should have an Advanced Programmers Group in town. I suppose the XP group (which I’ve never attended — their meetings seem to be very infrequent) and the Ruby group are the closest we have. This topic would be great for a group like that.

In the meantime, I guess I’ll give SVK a try, and see if it works for me.

]]> by: Kyle Cordes http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9836 Sun, 10 Jun 2007 16:54:08 +0000 http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9836 As far as I can tell from looking around at various tools, for the situation you describe (you want some distributed features, with a central SVN repo), SVK is the obvious choice. It is designed for that use case (though perhaps not exclusively for that use case). You can probably accomplish something like this with most of the other distributed tools. I've experiment with that using both bzr and git. I've though of giving a talk on this subject (using a distributed source control tool, on a project which has a central repo in a legacy centralized source control system); but I haven't figured out where to offer such a talk. As far as I can tell from looking around at various tools, for the situation you describe (you want some distributed features, with a central SVN repo), SVK is the obvious choice. It is designed for that use case (though perhaps not exclusively for that use case). You can probably accomplish something like this with most of the other distributed tools. I’ve experiment with that using both bzr and git.

I’ve though of giving a talk on this subject (using a distributed source control tool, on a project which has a central repo in a legacy centralized source control system); but I haven’t figured out where to offer such a talk.

]]> by: Craig Buchek http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9833 Sun, 10 Jun 2007 15:18:36 +0000 http://kylecordes.com/2007/06/08/svnsync-svn-backup/#comment-9833 I'm just getting the hang of Subversion. I've got a repository on a server, and do my work on my notebook. I like Subversion, but I want something that I can use off-line. In some ways, I'm just looking for something that will proxy svn actions and cache them until I get online. But I guess that's not really a feasible idea, since the repository could change, and the proxy would not know how to handle it. So I'm looking for suggestions and comparisons between the distributed version control systems. I like the way SVK lets me leverage my existing Subversion repository and tools. How do other systems compare? I’m just getting the hang of Subversion. I’ve got a repository on a server, and do my work on my notebook. I like Subversion, but I want something that I can use off-line. In some ways, I’m just looking for something that will proxy svn actions and cache them until I get online. But I guess that’s not really a feasible idea, since the repository could change, and the proxy would not know how to handle it.

So I’m looking for suggestions and comparisons between the distributed version control systems. I like the way SVK lets me leverage my existing Subversion repository and tools. How do other systems compare?

]]>