Hi Daniel, Daniel Shahaf writes: > Or, you could have svnrdump report the highest revision it dumped, and the > admin can remember that and invoke svnrdump -r N+1:HEAD next time. (Much > cheaper than parsing the entire dumpfile --- which you would have to do in > order to figure how many revisions it contains.) > > (One can parse that already out of the "* Dumped revision %ld" notifications; > if this use case is important, we may want to have a switch to suppress all > but > the last notification...)
Ah, excellent suggestion! :) Only, I wonder what'll happen if the connection breaks after the last revision has been partially dumped- can we just look for "^Revision-number: \d+$" from the bottom of the file, clean it up and then resume? -- Ram
