On Wed, 2008-07-02 at 17:50 -0400, Karl Fogel wrote:
> Julian Foad <julianfoad_at_btopenworld.com> writes:
> > On Wed, 2008-07-02 at 19:09 +0100, Julian Foad wrote:
> >> The "proplist" command ignores or wrongly interprets a peg rev specifier
> >> "@BASE":
> >>
> >> > $ svn ps testprop val foo
> >> > property 'testprop' set on 'foo'
> >> >
> >> > $ svn pl -v foo_at_BASE
> >> > Properties on 'foo':
> >> > testprop : val
> >>
> >> Argh! That's wrong. The BASE has no such property, as I haven't
> >> committed it yet.
> >
> > D'oh, I'm stupid.
> >
> > That's a peg rev. It doesn't change what the operative revision is. For
> > that I need:
> >
> >> $ svn pl -v -rBASE foo
> >
> > Exactly right.
>
> Well, wait. I'm not so sure you were wrong. Although operative revs
> and peg revs can mean different things in some circumstances, often they
> end up meaning the same thing, and this would be one of those times.
> foo_at_BASE is the revision of 'foo' as found in its BASE revision (IOW:
> interpret what revision BASE should be, go to that rev, find the path
> 'foo' in it, and that's our file).
It depends whether the operative revision defaults to the peg revision.
It doesn't, here. If it did, then we'd get the behaviour I expected and
you expect.
I couldn't remember which way round it's meant to be, which is why I
assumed I must have been wrong, but now you mention it maybe the
operative rev IS supposed to default to the peg rev. Yes, I think that
makes sense...
In that case, there IS a bug.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-03 00:03:46 CEST