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

RE: needs-lock always on?

From: Shatzer, Larry <Larry.Shatzer_at_MIROtechnologies.com>
Date: 2006-05-25 00:06:35 CEST

I found this to be the case when I had pushok's svn plugin installed. (Was
going to try it with something, and never got around to it). After I
uninstalled their program, it stopped doing that.

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Frits Hilderink
> Sent: Wednesday, May 24, 2006 2:41 AM
> To: users@tortoisesvn.tigris.org
> Subject: svn:needs-lock always on?
>
>
>
> I'm using Subversion 1.3.1 with 'svnserve' for a few weeks
> now and it works
> just great. My repository uses the Berkeley DB.
>
> I want to use the copy-modify-merge way but everytime i
> commit a *.c source
> then it is automatically set to 'read-only'. There is no
> 'needs-lock' property
> set.
>
> Can anyone tell me if i'm doing something wrong?
>
> If i'm correct then the copy-modify-merge is the default
>
> Available version information:
> TortoiseSVN 1.3.3, Build 6219 - 32 Bit
> Subversion 1.3.1,
> apr 0.9.7
> apr-iconv 0.9.7
> apr-utils 0.9.7
> berkeley db 4.3.28
> neon 0.25.4
> OpenSSL 0.9.8a 11 Oct 2005
> zlib 1.2.3
>
>
> Frits
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu May 25 00:09:54 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.