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

Re: Optional | Compressed text-base storage

From: Olivier Sannier <obones_at_free.fr>
Date: 2005-06-23 11:40:01 CEST

Dylan Leigh wrote:

>Looking over the posts here, the solution which would probably please
>everyone is to have a "wcstorage" property, which can then be
>overridden by a config file entry (so users who don't want the feature
>can turn it off for all their copies), which in turn is overridden by
>an element in the .svn directory itself.
>
>
Yes, but there should be a possibility to set a default value so that
newly created directories inherit from it.

>On the other hand, I'd much rather get compression working and stable
>on the client end first without touching any server code or . Also, I agree
>with Scott Palmer's post that a master
>
>
A master what? Anyway, yes, having it on the client side first would be
a very good thing, the server setting could wait. It's just a matter of
convenience for admins.

>Zlib is my suggestion to do the actual compression; its portable,
>unencumbered and has reasonable performance. It's also required by
>neon so many svn installations have it.
>
>
Sounds good to me as well.

>The config setting would have a set of simple rules to apply to each
>file when added, imported, checked out etc; something like:
>
>
<snipped>

This looks to me like a very finely grained set of options. I mean sure
it would be good to go down that much detail, but is it really necessary
for a first implementation?
Couldn't it be possible to start with an on/off situation and move on to
more complicated stuff when this has been proven to work?

My 2 cents
Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 11:41:28 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.