My follow up question was going to be what does it mean.
You have a lot refactoring to do on this code after 1.0.
I raised issue #1596 against the misleading help. You will
be pleased to hear that the subversion book is clean on this
issue.
Barry
At 08-11-2003 08:20, C. Michael Pilato wrote:
>Philip Martin <philip@codematters.co.uk> writes:
>
> > Barry Scott <barry@barrys-emacs.org> writes:
> >
> > > I want to add support for all the client commands that take
> > > --revision X:Y to pysvn.
> > >
> > > But I haven't figured out how revision ranges work. I'd appreciate
> > > help from someone that understands how the C API manages to discover
> > > the end_revision that is parsed.
> > >
> > > Why does the svn C client API only take one of the pair as a
> > > parameters? For example svn_client_checkout.
> >
> > The option parsing code in svn is common to all the subcommands, thus
> > all the subcommands accept -rX:Y at option parsing time, even though
> > some of them can only handle the -rX form. The subcommands that only
> > handle the -rX form should produce an error if invoked with -rX:Y,
> > unfortunately not all of them do, some silently ignore the :Y part.
>
>To answer one of the questions that Philip did not:
>svn_client_checkout() and other client functions that take only one of
>the pair do so because those are operations for which a *range* of
>revisions make no sense. What does it mean to checkout a range of
>revisions? Or update to a range of revisions?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 8 19:05:53 2003