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

Re: Some peg rev help text missing from command-line client

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-05-09 19:34:58 CEST

On Tue, 09 May 2006, C. Michael Pilato wrote:

> Daniel Rall wrote:
> >>Only thing that seems wrong in this list is 'switch' -- can we not use the
> >>peg-rev syntax with 'svn switch'? If not, that's a(n admittedly minor)
> >>shortcoming.
> >
> > Yeah, I debated on that one (which also applies to 'switch
> > --relocate'). Neither prototype from svn_client.h includes a peg rev
> > parameter:
> >
> > svn_error_t *
> > svn_client_switch(svn_revnum_t *result_rev,
> > const char *path,
> > const char *url,
> > const svn_opt_revision_t *revision,
> > svn_boolean_t recurse,
> > svn_client_ctx_t *ctx,
> > apr_pool_t *pool);
...
> > While a peg rev for the PATH parameter seems fairly redundant with
> > RESULT_REV, perhaps I should provide it for the sake of UI
> > consistency? Looks like this would involve rev'ing the
> > svn_client_switch() API.
>
> RESULT_REV tells the revision number that you were switched to, and is not
> the same as a peg revision. (It's more closely related to the REVISION
> argument, which can represent a revision number or revision keyword.)
...

Mike, would you mind describing how the use cases for the following
commands differ?:

  svn switch -r37 http://repos-host/svn/branches/foo

  svn switch http://repos-host/svn/branches/foo@37

I'd have thought both commands were intended to "switch my working
copy to the 'foo' branch as it looked in r37."

-- 
Daniel Rall

  • application/pgp-signature attachment: stored
Received on Tue May 9 19:44:53 2006

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.