[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: read-only checkouts

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-02 18:50:48 CEST

On Apr 2, 2005, at 9:07 AM, Patrick Hanna wrote:

> it just prevents a user from accidentally modifying some portion of
> the source because they have not explicitly checked out that file for
> editing.

I don't understand why this is a problem, or what great catastrophe
you're trying to prevent. As you said, it's not about locking files,
it's about forcing users to "declare" the files they intend to change.

My understanding is that some systems (like clearcase or perforce)
behave this way, but I don't suspect Subversion will ever grow such a
feature. The 'svn status' command shows exactly what you've edited.
If you can teach users declare the files they want to edit, it seems
just easy to to teach them to run 'svn status' early and often, and
especially before running 'svn commit'.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 2 18:54:46 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.