[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: Eric Lee <eric_at_myprojects.srhost.info>
Date: Fri, 25 Jul 2008 00:17:08 +0800


Can you check the wc folder you are in ?

Right click the wc folder and choose property to see
the readonly checkbox was selected or not.

If so, unselected it and apply, on a dialog it pop-up.
Click apply to files and all files and folders option.

Also, you may also need up one more level and do this same check.

Wish this help.

Get subversion, phpBB 3
  ----- Original Message -----
  From: smolki81 Gazeta.pl
  To: users_at_subversion.tigris.org
  Sent: Thursday, July 24, 2008 9:16 PM
  Subject: Why svn marks all touched files as readonly after each operation? How to disable it?

  Every time I do commit or checkout on some files, they are marked in my working copy as readonly. 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.

  I'm new to Subversion and this list, so please be forgiving.

  Thank you,
Received on 2008-07-24 18:17:44 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.