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

Re: Crazy 5-step plan to remove the cached pristine copy

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-03-24 17:37:51 CET

On Mon, 2003-03-24 at 10:50, Stefan Monnier wrote:
> Why exactly would you want to remove the cached pristine copy ?
> Is it the disk space that's bothering you ?
> It seems the disk space should be rather small: all unmodified files
> can be hardlinked to their pristine copy, so disk space is only needed
> for the few modified files.

Bitkeeper supports this trick, I've heard, but it only works if you
carefully assure that your editor modifies hard-linked files by
replacing them. (emacs does not work this way by default.)

In Subversion, there is also the complicating factor that the text-base
is not generally identical to the working copy file, because the
working-copy file has been newline-translated and keyword-expanded while
the text-base has not. That could be changed, but it would be a change
of comparable complexity to making the wc library handle not having a
text base.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 24 17:38:40 2003

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

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