RE: Eliminating the text-base penalty

> Option 2 is to implement read-only working copies. The idea here is
> that, given the appropriate checkout option, files are checked out

My two cents:

I actually don't care too much about the "extra" copy of each checked
out file (disk is cheap!). However, I like working in a command-to-edit
mode, because it allows the source control system to know what it needs
to inspect for "diff" or "checkin" operations -- only actually edited
files are actually considered; no stat-ing of 18,000 files just to
figure out what to do.

Note that the "edit" operation COULD be done off-line in Subversion,
because you already have the file, and SVN likes to keep client-side
state (Perforce doesn't). However, when on-line, it would be useful if
you got a warning if the file you're editing is newer in the repository.

This is, in my opinion, one of the better features of Perforce (together
with bunched atomicly commited change lists). If you could do BOTH in a
new too, why, I'd save $150/year/person :-)

Cheers,

                        / h+

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 26 19:30:49 2002