Re: TSVN Operations on read-only and locked files

Dave Lawrence wrote:
> Don't know whether these are TSVN issues or SVN issues but:
>
> 1) Read only files: Prior to TSVN1.4 doing an update preserved
> (reinstated) the read-only status of the file after the udpate. Now the
> file is instead left writable after update.

That would be a Subversion issue.

> 2) File not writable due to being used by another process: Update fails
> (as you would expect) but then .svn directory is left in a corrupted
> state, cannot fix using cleanup. The only fix I've found for this is a
> fresh checkout.

That is a Subversion issue too and outside of TSVN's realm.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org