Another Thought on .svn Size

At the risk of getting fired at, the size of the .svn directory has me
somewhat concerned, too. The way I'm used to doing things involves a lot of
work on usually just a limited subset of a large working copy.

Perhaps another way to get the same functionality as now without the size is
to use a lazy .svn:

At checkout the .svn directory gets a list of signatures of all files
(something like a checksum, see the project 'makepp' at sourceforge.net).
Any svn operations first compare the signatures to see if there are any
changes and, if so, then get the pristine copy of that file to put into the
.svn directory and procede as usual. At commit time, the signature could be
renewed and the pristine copy in .svn removed again.

As someone suggested, there might be several methods the administrator or
user could choose for himself: (1) full .svn as now, (2) something like my
suggestion, or (3) something else--by choice at checkout (and of course able
to be changed during the lifetime of the workspace).

Tom Browder

PS. I apologize if I've appeared to steal someone else's ideas. I've tried
to read all posts on this thread but may have missed something.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 12 11:46:58 2004