If you can't figure it out yourself, don't hesitate and write a bug report. Please include the version you're running (output of
fsvs -V), the command line you're calling fsvs with, and the output it gives.
Furthermore it might help diagnosing if you tried with the -v parameter, and/or with -d; but please mind that there might be data in the dump that you don't want to make public -- if you're not sure, ask on the mailing lists.
Send these things along with a description of what you wanted to do to
email@example.com or, if you like that alternative better, just file an issue.
(The bugs I find and the things on my
TODO are not in the issue tracker, as I can't access it while on the train - and that's where I spend the most time working on fsvs).
Please be aware that I possibly need more details or some other tries to find out what goes wrong.
TODOfile, pick your favorite point, and implement it.
If you don't know C, but another programming language (like perl, python, or shell-programming), you can help, too -- help write test scripts.
I mostly checked the positive behavior (ie. that something should happen given a set of predefined state and parameters), but testing for wrong and unexpected input makes sense, too.
If you don't know any programming language, you can still look at the documentation and point me to parts which need clarifying, write documents yourself, or just fix mistakes.
All contributions should please be sent as a unified diff, along with a description of the change, and there's a good chance to have it integrated into the fsvs code-base.
"svk diff"commands should do what you want.
.tar.bz2, keep a pristine version in some directory and make your changes in another copy.
diff -ur \e original \e new > \e my-changes.patch