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

Re: Locking issues

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-14 03:55:02 CEST

On Apr 13, 2005, at 8:28 PM, Philip Martin wrote:

> Ben Collins-Sussman <sussman@collab.net> writes:
>
>> 'svn info' is behaving just like any other command that needs to
>> locate a repository object, isn't it? It's following copy-history
>> just like everything else. Are you saying it shouldn't?
>
> Perhaps you misunderstood, it doesn't matter what revision I pass as
> -rX, if I don't use @head I don't see repository locks. So
>
> $ svn info -rhead wcpath
>
> doesn't show repository locks, but
>
> $ svn info wcpath@head
>
> does show them. Using a numeric revision
>
> $ svn info wcpath@N
>
> doesn't show repository locks, even when N is the same as head.
> However
>
> $ svn info -rN wcpath@head
>
> does show repository locks even when N is not the same as head.
>
> I find that behaviour surprsising, I would expect the peg revision to
> matter when determining which URL to query, but I can't see why it
> should affect whether lock information is requested.
>

Hm, I guess you're right, that *does* seem like a bug. If you don't
have time to investigate, can you file the bug, so that I'll remember
to look at it tomorrow?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 14 03:55:52 2005

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.