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

AW: Why does "Add..." to working copy automatically set "svn:needs-lock" property?

From: Grothaus, Christoph <C.Grothaus_at_LRworld.com>
Date: Tue, 16 Aug 2011 08:52:58 +0200

> * Try the SVN commandline under win32 instead of Cygwin, those can be considered different operating systems. The native win32 CLI would use the same configuration files as TSVN, but it wouldn't use any "tsvn:..."
> properties.
> * Check the parent folder[s] in the repository, not just in the working copy.
>I'd be surprised if this gave any different results though...

Hej Uli,

I found the reason.

You were right. The native win32 client uses other configuration files than the cygwin client. I perfectly know about the config file in my Windows user profile, and had already double checked it and checked it again. No auto-props there.

But somehow our IT department has setup our initial PC installation in a way that there is also a config file in the "All Users" section. And voilà, there in the auto-props section, I see a line "* = svn:needs-lock=true".

So, no dodgy behaviour of any client (btw., the Eclipse "Subclipse" plugin showed the same behaviour), but everything can be perfectly explained.

Thanks a lot



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-16 08:53:21 CEST

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.