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

Read-only checkouts/updates

From: Rick Mann <rmann_at_latencyzero.com>
Date: 2005-06-08 01:22:27 CEST

I read the thread on read-only checkouts, and it seems to have
wandered from what the original poster asked for. I am in the same
boat as the original poster:


> Is there a method for obtaining a module that creates a read-only copy
> of the module? This way, if a developer wants to edit the file,
> they can
> then specifically checkout the file for editing. This will prevent
> accidental editing of files that a developer may not need to edit.
> Thanks,

I need for my working copy to be read-only. I don't want to lock
files for exclusive checkout, and I'm happy to use other tools to
make the file writable when I choose to edit it (my IDE asks me if I
want to make a file writable as soon as I try to type in it).

It's too easy to unwittingly modify a file otherwise. And because SVN
doesn't support partial checkins, it's a HUGE pain to determine that
a file should not be checked in.

This feature can be entirely client-side, and turned off by default,
but even crummy CVS allows this functionality.

Is this being considered for short-term implementation, and if not,
why not? If it's a reasonable request, should I add an Issue for it?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 8 01:24:28 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.