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

Fwd: snv --no-unlock confuses me

From: johan laenen <johan.laenen_at_gmail.com>
Date: 2005-05-19 15:12:05 CEST

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
Received on Fri May 20 16:49:06 2005

This is an archived mail posted to the Subversion Users mailing list.