[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Hows does the C API find the end_revision?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-11-08 09:20:53 CET

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 09:21:54 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.