Daniel Rall wrote:
>
> The global switch is a strong stride in the right direction, but even more
> useful is the pattern/WC granularity Philip suggests. Being able to enable
> this feature on a per-file type matches my use case (probably by inspecting
> svn:mime-type and/or pattern matching the file name against some sort of glob
> expression). For instance, I might want to turn this on for files of type
> "text/*", and extensions *.txt, *.xml, *.html, etc. I would not want to
> enable this feature for binaries (e.g. "application/*" or *.exe).
The only reason I can imagine you would want to bother explicitly disabling
this feature for binaries is because it is inefficient for them (taking
significant time for insignificant space saving). Do you know in advance that
the implementation will be inefficient enough to make that degree of control
worthwhile? And if it is, I would much prefer the software to determine this
for itself and automatically refrain from compressing such files. Yes, that
may be hard to design and will occasionally make the wrong choice, but
providing the user with controls to tweak the internal operation of subsystem
that should be opaque is nasty. Providing user controls for this behaviour
should be a last resort.
The degree of control that we provide should be the minimum necessary.
Ideally, given automatic avoidance of wasting time on incompressible files, I
would expect this to be per combination of machine (processing power) and file
system (disk space). In practice, a per-user configuration is probably the
closest convenient match to that, suitable for most users.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 20 00:40:19 2005