[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: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 7 Jan 2008 17:09:43 -0400

On 1/7/08, Robert Dailey <rcdailey_at_gmail.com> wrote:
> My responses are interleaved below.
> On Jan 7, 2008 1:09 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> > But what if I deliberately set a file read-only, and don't want it
> > un-set? Software shouldn't circumvent my wishes like this.
> You don't do this. Read-only property for versioned files is reserved for a
> specific meaning to Subversion, that is, to represent locked items. There's
> really no valid reason that I can think of to break this meaning through
> some form of inconsistency.

No, it uses read-only to indicate that a file *requires* a lock. If
you lock the file, read-only is unset. If file which does not require
a lock is locked in another WC (yours or someone else's), your WC
won't be updated to set read-only on that file.

I can think of plenty of reasons why I would want to change read-only
on a file in my WC. Subversion shouldn't question me as to *why*. My
WC is mine, not Subversion's.

> Having said that, I still see no reason why
> having the cleanup feature do what I previously explained be a bad idea.

Because I may have a valid reason outside Subversion. By this same
line of reasoning, you might also suggest that Cleanup should remove
any non-versioned files or file metadata.

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-07 22:09:48 CET

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.