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).
Why shouldn't svn interpret that correctly? And why would a local
propchange be visible on that revision of the file?
---------------------------------------------------------------------
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-02 23:51:51 CEST