Checking out files to default to read-only

["Thompson, Graeme (AELE)" <Gr...@smiths-aerospace.com>]

Hi,

Is it possible to have files marked as read-only when you do an
update/checkout?

This would stop the IDE from making unnecessary, and sometimes
incorrect, changes to files.

On a further point - are there any plans to enhance subversion to allow
it to work in a lock/unlock system exclusively. i.e. to work using the
methodology applied with PVCS, VSS and other version control systems?

We have had issues with the merge methodology.

I have read http://svnbook.red-bean.com/

And am going to read
http://www.phptr.com/content/images/0131855182/downloads/Nagel_book.pdf

Thanks,

Graeme

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Checking out files to default to read-only

[Paul Koning <pk...@equallogic.com>]

>>>>> "Graeme" == Graeme Thompson <Thompson> writes:

 Graeme> Hi,

 Graeme> Is it possible to have files marked as read-only when you do
 Graeme> an update/checkout?

 Graeme> This would stop the IDE from making unnecessary, and
 Graeme> sometimes incorrect, changes to files.

Call me old fashioned, but I'd say that an IDE that makes changes to a
file without being asked to is junk and should be tossed in the trash.

     paul


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Checking out files to default to read-only

[Mark Phippard <ma...@softlanding.com>]

"Thompson, Graeme (AELE)" <Gr...@smiths-aerospace.com> wrote on 
12/05/2005 10:09:03 AM:

> Is it possible to have files marked as read-only when you do an
> update/checkout?
> 
> This would stop the IDE from making unnecessary, and sometimes
> incorrect, changes to files.
> 
> On a further point - are there any plans to enhance subversion to allow
> it to work in a lock/unlock system exclusively. i.e. to work using the
> methodology applied with PVCS, VSS and other version control systems?
> 
> We have had issues with the merge methodology.
> 
> I have read http://svnbook.red-bean.com/
> 
> And am going to read
> http://www.phptr.com/content/images/0131855182/downloads/Nagel_book.pdf

This was all addressed in Subversion 1.2.

Set the property svn:needs-lock on any file that you want to have 
read-only on checkout.  Use the svn lock/unlock commands to lock the file 
and make it editable.  Etc..

Mark



_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org