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

Re: Clean Up & Read-Only Files

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: Wed, 9 Jan 2008 14:35:11 -0600

On Jan 9, 2008, at 06:13, Andy Levy wrote:

> On Jan 8, 2008 9:58 PM, Ryan Schmidt wrote:
>> On Jan 7, 2008, at 14:40, Robert Dailey wrote:
>>> Would it be possible for the "Clean Up" operation in TortoiseSVN to
>>> make read-only files that were not made so by locking writable? For
>>> example, say I deliberately go to file properties for a versioned
>>> file in my working copy and make it read-only. If I do a clean-up,
>>> it should see that this file is read-only when i do not own a lock
>>> (or if there was no lock to begin with) to that file. It should
>>> then proceed to remove the read-only attribute from the file.
>> I don't see why Subversion should do this. What's your justification
>> for this proposed change?
> For reference, the original thread on the TSVN mailing list:
> http://svn.haxx.se/tsvnusers/archive-2008-01/0087.shtml

Ok, I've read the original thread now. Robert, quoting your message
from TSVN Users:


On Mon, 7 Jan 2008 16:05:44 -0600 Robert Dailey wrote:

> I'm manually copying files from a team foundation server to my SVN
> repository, which yields many read-only files that need to be
> converted to
> writable status after being moved to my SVN working copy directory.
> Doing
> this through windows explorer is a very slow process as the ratio of
> writable files to read-only files is probably 10,000:1. The Cleanup
> feature,
> which seems a lot smarter than a generic tree search, could
> probably achieve
> this goal much quicker for me.

It seems your problem of undesirably read-only files originates
outside of Subversion. Therefore, it's really no business of
Subversion's to fix it for you, especially since, as Andy pointed out
in the original thread, Subversion has no way to know that the read-
only attribute is unintended. Subversion is not a generic file
attribute modification tool, and "svn cleanup" exists for the sole
purpose of getting the working copy back into a usable state after a
Subversion process has crashed or been unexpectedly interrupted.
Arbitrarily changing the read-only attribute of files is not
necessary to accomplish that goal. It sounds like all you really want
is a script which can remove the read-only attribute of many files at
once. So you should write such a script, or find one that someone
else has already written. This function doesn't belong in Subversion.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-09 21:36:13 CET

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.