On Sat, Nov 08, 2003 at 02:20:53AM -0600, C. Michael Pilato wrote:
> Philip Martin <email@example.com> writes:
> > Barry Scott <firstname.lastname@example.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?
At least in perforce terms, updating to a range of revisions means to update
the files changed in those revisions to the latest included revision in which
they were changed.
This can be very helpful if you update to a build lab label, which then has
build break fixes applied to it.
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Sat Nov 8 21:35:18 2003
- application/pgp-signature attachment: stored