Re: text-base penalty: A proposed solution

I'll just throw this out because nobody has mentioned it yet:

Some kernel developers I know make heavy use of trees of hardlinks.
If you make sure your editor creates a new file on save then this
essentially gives you a large number of copy-on-write trees. Not only
are they cheap in disk space, but it also saves buffer memory and
makes a smart diff run quickly.

I wonder how well Subversion would cope with the text-base being
initially a hardlink to the working copy? Or with two wcs that are
mostly hardlinks?

The drawback is that if your editor doesn't break the link and
therefore also writes to text-base then things will get very
confusing.

Some wise person wrote "more computing sins have been committed in the
name of efficiency (without necessarily achieving it) than for any
reason."

If your trees are this big it might be time to split them into
modules. (I suppose if they're that big and that old then it's
infeasible though.)

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