You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by johan laenen <jo...@gmail.com> on 2005/05/19 13:12:05 UTC

Fwd: snv --no-unlock confuses me

Hi,

I'm using svn, version 1.2.0 (Release Candidate 2) on Win 2000.

For my binaries I'm using svn:needs-lock. Binaries arrive in my
working copy as read-only. When I lock the binaries they become
read/write.

So far so good.

When modifying my binaries and issuing a commit with --no-unlock my
locks in the repository stay but my files in the working copy become
read-only.

This puzzles me. I'd expect the files in the working copy keeping
their read/write status untill I give up my lock completely.

Is this normal behaviour or a bug?

Greetings,

Johan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: snv --no-unlock confuses me

Posted by Ben Collins-Sussman <su...@collab.net>.
On May 19, 2005, at 8:12 AM, johan laenen wrote:
>  status untill I give up my lock completely.
>
> Is this normal behaviour or a bug?


Whatever it is, it's not a reproducible bug (for me) using the latest  
client.  Try upgrading to svn 1.2.0-rc4 and see if it still happens.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Fwd: snv --no-unlock confuses me

Posted by johan laenen <jo...@gmail.com>.
>> I'm using svn, version 1.2.0 (Release Candidate 2) on Win 2000.

>> For my binaries I'm using svn:needs-lock. Binaries arrive in my
>> working copy as read-only. When I lock the binaries they become
>> read/write.

>> When modifying my binaries and issuing a commit with --no-unlock my
>> locks in the repository stay but my files in the working copy become
>> read-only.

The problem got solved in rc4. I'm not experiencing it anymore.

Thanks for helping me out,

Johan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org