RE: Checkout every file as read-only; make some of them editable with a explicit command.

Hello,

> Unfortunately, we have no plans to emulate the CVS read-only feature
> you're talking about. In SVN's upcoming design, a read-only file means
> "it must be locked to be edited". There's no read-only concurrent
> files.

        Take a look at this program (I found it while searching for a solution to
this problem):

http://www.pushok.com/soft_download.php?idprogram=3

"
General Information:

[...]

2. We compelled to make patch to current SVN code to solve few problems with
compatibility with IDE. We do believe that this patch will be included in
later version of SVN. Just for now, if you want better compatibility of your
SVN clients and IDE, we suggest to use patched versions of SVN clients.
Patches have following abbreviations

[...]

* CR - patch that mimics "Checkout read-only" option of CVS. Makes newly
pulled and committed files read-only.

[...]"

        As far as I can tell, this issue is (somehow) implemented on the
client-side in these customized TortoiseSVN clients; perhaps this way such a
feature need not be considered at the server-side: conflicts that ocurr on
files that were checked out as read only and then made writable could be
treated as normal conflicts (the ones that may happen in files what are
checked out in normal, read/write mode).

        Just a clarification: I'm not endorsing this program; as a matter of fact,
I haven't even tried it.

Greetings,
Esteban.

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.3.1 - Release Date: 15/11/2004
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org