svncutter - Not planning to let the perfect be the enemy of the good

Learning that svndumptool.py exists has confused my plans for
svncutter somewhat. My program does two things svndumptool.py doesn't,
"squash" and "setlog". The setlog function is pretty trivial, but getting
squash right is rather tricky. On the other hand, svndumptool.py is a much
more general tool with dozens of interesting capabilities mine
doesn't have.

In an ideal world, the code for squash and setlog would merge into
svndumptool.py (and svndumptool.py would become part of contrib/). Alas,
the svndumptool.py guy is not responding to email.

On the one hand, I don't want to put a lot more effort into svncutter
unless I know the merge isn't going to happen. I've suspended my plans
to write unit tests and the directory-lifting function that svndumptool.py
apparently duplicates. On the other hand, svncutter is a significant
improvement over svnsquash, and I'd prefer people actually got to use
it rather than having it gather dust on my hard drive.

Accordingly, I'm enclosing it to replace svnsquash in contrib/. I'll
continue trying to reach out and open a collaboration with the
svndumptool.py maintainer.

-- 
		Eric S. Raymond