Re: Compressed text-base patch

>>>>> "ED" == Eric Dorland <eric.dorland@mail.mcgill.ca> writes:

ED> After a few weeks of work on and off, here's my first stab at a
ED> compressed text-base patch.

Out of curiosity, what motivates you to compress text-base in
the first place? Is it to save disk space for the working copy?

Since compressed text-base would make it slower to run working
copy operations like "svn diff", this approach would rely on an
assumption that most of the time, most of the files checked out
into the working copy are not modified, especially in a large
project where it matters. And I think it is a valid assumption.

If that assumption holds, however, I wonder if it would be
simpler just to make checked-out files read-only by default, and
make text-base hardlinks to them. This would further save the
client side diskspace. Perhaps you can add a new command "svn
edit" that breaks the hardlink and make the working copy file
writable.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 03:35:54 2003