Pietro Abate homepage

I'm definitely fed up with the lack of feature of svn. I always end up making backup copies of files, committing the wrong patch set, being unable to cherry-pick what to commit, not to talk about branching, merging and other marry activities. So today I overcome my laziness and setup a git svn repository for dose3 (since it's all there, go ahead, and be happy!).

The concept of git svn if pretty easy. You work with git, and from time to time, you commit in svn.

Recently I had few problems with a svn repository that is shared between multiple ssh users. I followed the instructions in the svn book and to solve the problem once for all I recreated the repo from scratch. Briefly:

hopefully this is gonna work.

A while ago one of my svn repositories became all the sudden inaccessible. It turned out that the file db/current got corrupted for some reason, leaving the repo in an inconsistent state.
The file db/current in a svn repository (using the FSFS backend) contains the largest revision number and the next unique node and copy ids. Googling around I found this old message [1] explaining the problem, but not providing any satisfactory solution.

This is a small script to generate code snapshots from the svn repository.