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

Re: Why svn marks all touched files as readonly after each operation? How to disable it?

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Thu, 24 Jul 2008 17:01:19 -0500

On Jul 24, 2008, at 08:16, smolki81 Gazeta.pl wrote:

> Every time I do commit or checkout on some files, they are marked
> in my working copy as readonly.

Odd; I've never experienced that.

> It is unconvenient for me to unmark readonly status on each file
> after each SVN operation, so I seek for some way to disable this
> behavior. Since I didn't found any clues on documentation
> (according to it, files should not me marked as readonly, but I'm
> new to SVN so don't really know), maybe some of you feels the same
> as me and found solution?
> I'm using windows svn client 1.4.6 version. I installed Tortoise,
> and it seems to mark all touched files as readonly too, just as svn
> client. I installed standard svn server, and checked visualsvn
> server, still, the behavior remains the same. Checked on two
> different PCs, with two different versions of Windows.
> So how can I configure svn client (or Tortoise, or whatever) to not
> to mark files on working copy as readonly after each commit or
> update? I believe it was introduced for purpose, but I do not see
> the point, and it only trouble me.

Do any of these files have the svn:needs-lock property set? If so,
then it is normal and expected and desired for Subversion to mark
them as read-only, until you acquire the lock.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-25 00:01:47 CEST

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

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