Great, thanks (in a fixing-broken-windows sense; svnrdump itself is still unusable-or-unsafe without sane revision number handling.)
(I did discover "Tailor", http://progetti.arstecnica.it/tailor/ which was actually the first tool to *work* on the original task, I'm surprised it doesn't get more attention... though as far as I can tell, it works purely with a combination of the client command line interface and rsync :-) On Fri, May 13, 2011 at 5:21 PM, C. Michael Pilato <cmpil...@collab.net> wrote: > On 05/13/2011 05:13 PM, C. Michael Pilato wrote: >> On 05/12/2011 04:26 PM, Mark Eichin wrote: >>> The third bug is that "svnrdump -r 3:HEAD" says "E205000: Unsupported >>> revision specifier used; use only integer values or 'HEAD'" (which is >>> why the attached script goes out of its way to parse revision numbers >>> out of "svn info" -- -r 3:7 works fine.) Even if there's a reason to >>> not support HEAD (though I kind of doubt that) the error message >>> itself is inconsistent :-) >> >> This is just a coding problem. (Probably my own.) I'll see about fixing >> this one in the next few minutes. > > Committed. > > $ cat ~/log_message.txt > Fix a silly buglet: > > $ svnrdump dump -r4:HEAD file:///path/to/repos > svnrdump: E205000: Unsupported revision specifier used; use only > integer values or 'HEAD' > > * subversion/svnrdump/svnrdump.c > (validate_and_resolve_revisions): Resolve revisions of kind > svn_opt_revision_head to the HEAD revision (which we conveniently > have as 'latest_revision'). > > Reported by: Mark Eichin <eic...@gmail.com> > $ svn ci -F ~/log_message.txt > Sending subversion/svnrdump/svnrdump.c > Transmitting file data . > Committed revision 1102901. > $ > > > -- > C. Michael Pilato <cmpil...@collab.net> > CollabNet <> www.collab.net <> Distributed Development On Demand > > -- _Mark_ <eic...@thok.org> <eic...@gmail.com>
