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

I'm sorry, I believe you are correct. I usually associate read-only
mode with exclusive locks. I guess they can be two different features.
:-)

Google didn't find anything about this in the subversion book
(http://svnbook.red-bean.com/). Maybe someone else has a more definite
answer for you?

-petri

-----Original Message-----
From: Esteban Bolanos [mailto:ebolanos@datatec-ec.com]
Sent: November 16, 2004 11:16 AM
To: Petri Varsa
Cc: Subversion Users
Subject: RE: Checkout every file as read-only; make some of them
editable with a explicit command.

Hi,

        I'm looking at the roadmap right now. Are you referring to the
"optional
locking (reserved checkouts)" feature? I might be wrong, but I believe
that
that is a different thing: it is a feature that allows for a file to be
edited only in one working copy at a time. That's not what I'm looking
for.

        Perhaps you are referring to a different 1.2 feature? Which one
would that
be?

Thanks,
Esteban.

> -----Original Message-----
> From: Petri Varsa [mailto:petri.varsa@desire2learn.com]
> Sent: Martes, 16 de Noviembre de 2004 11:03
> To: Esteban Bolanos
> Cc: Subversion Users
> Subject: RE: Checkout every file as read-only; make some of them
> editable with a explicit command.
>
>
> Version 1.2 is supposed to have this feature. I don't know when 1.2
is
> supposed to be released, but the subversion roadmap mentions this
> feature.
>
> http://subversion.tigris.org/roadmap.html
>
> -petri
>
> -----Original Message-----
> From: Esteban Bolanos [mailto:ebolanos@datatec-ec.com]
> Sent: November 16, 2004 10:53 AM
> To: Subversion Users
> Subject: Checkout every file as read-only; make some of them editable
> with a explicit command.
>
> Hello,
>
> Is there a way to checkout files in read-only mode ("protected"
> files), and
> then enable the edition on just the files that one wants to work with?
>
> Some CVS users who are considering migrating to SVN asked me
> this, because
> that's a "feature" that they use frequently. I don't know much about
> CVS,
> but they tell me that, with it, it's possible to checkout files in
> protected
> mode and then issue a "cvs edit" command only on the files they intend
> to
> change, in order to prevent accidental changes. All that I know about
> "cvs
> edit" is that it is normally used in the context of watches; howewer,
> they
> don't use it for change notification, but rather just as a protection
> mechanism.
>
> How could one achieve a similiar effect in SVN?
>
> Thanks,
> Esteban.
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.795 / Virus Database: 539 - Release Date: 12/11/2004
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org