Alright, so does this mean you'll fix it to throw the error, or to handle
the date, or both? From what you said I'm guessing the error will be
thrown, and the date ignored. Of course, I'd prefer if the date worked,
but in the spirit of open source I'm guessing that's my problem =).
-Joe
On Mon, 22 Mar 2004, Julian Foad wrote:
> Joseph Dunn wrote:
> > I was writing a script to dump a repository on a regular basis. I wanted to use dates in the svnadmin dump command, but they don't work. This was brought up on the #svn irc channel and I was told to send en email to the dev list. To duplicate the problem simply take any svn respository and try to dump all revisions from a certain date forward. According to the documentation anywhere that a revision number can be used a date in {} can be used. However, although svnadmin dump checks the syntax of the date, but then dumps all revisions. If anyone would like an example repository, I have a sample one, but I don't see what it can tell you that I can't. Well, I'll use an svn log command to translate the dates into versions, but it'd be nice to be able to skip that step. Let me know if you need any other information.
>
> Thanks for reporting this. I can see in the code that the function 'subcommand_dump' does not currently handle the '{DATE}' method of specifying a revision. Unfortunately it does not throw an error, and just ignores the revision specification. It should throw an error for any revision specification that it cannot handle: not just dates, but also 'COMMITTED' etc.
>
> - Julian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 22 18:28:12 2004