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

Re: Using md5sum for svn status

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-27 14:43:49 CEST

On Apr 27, 2005, at 7:35 AM, Dirk Schenkewitz wrote:

> When I read the following, I had an idea:
> Ben Collins-Sussman wrote:
>> On Apr 26, 2005, at 11:57 PM, Peter McNab wrote:
>>>> I was looking at how TortoiseSVN stores a base working copy of
>>>> files with the WC, which is great for instant diff, but is not so
>>>> meaningfull for binary files.
>> This isn't TortoiseSVN, is this how the svn client libraries work,
>> it's not something you can turn off. It's not just for running 'svn
>> diff' without hitting the network, it also means you can 'svn revert'
>> without hitting the network, and it means 'svn commit' can send
>> binary diffs to the server, instead of the entire file.
>>>> We are hearing from folks on the list who have 500Mb binaries so
>>>> unnecessary download and local duplication of these might be a
>>>> productive goal for Subversion.
>> Yes, someday (i.e. svn 2.0) the cache-in-working-copy will be
>> optional.
> How about storing the "secret copy" as compressed files, as an option?
> This would increase the operating times very much, but it would save
> some disk space.

Yep, that's been discussed too. The current thinking is that the
text-bases will be a choice of {yes | no | compressed}.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 27 14:48:16 2005

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

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