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

Re: svn commit: r19782 - in branches/changelist-feature/subversion: include libsvn_client svn

From: David James <djames_at_collab.net>
Date: 2006-05-23 20:01:35 CEST

On 5/23/06, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> On 5/23/06, David James <djames@collab.net> wrote:
>
> > If I want to look for files from changelist foo in the whole wc, I'll
> > specify the path to the root of the WC like so:
> > svn status --changelist foo ~/wc/svn-trunk
> >
> > Maybe this is just my bias as a Subversion developer, but that's how I
> > expect Subversion to work.
>
> Your example violates our policy about all arguments being 'global',
> and being able to appear in any order. Anything which isn't an
> argument to a switch (--switch blah) is assumed to be a path or url
> target. In other words, our parser sees no difference between
>
> svn command --changelist foo /some/path
> svn command /some/path --changelist foo
>
> And, in both of these cases, the final target list is [/some/path,
> [members of changelist]].

I thought that 'foo' was an argument for the 'changelist option'. E.g.
  svn command --changelist=foo /some/path

These options can certainly be supplied in any order. For example:
  svn command /some/path --changelist=foo

foo is not a path, so it shouldn't be treated as such. It's an
argument to the 'changelist' option.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 23 20:02:18 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.