Perhaps it would be more intuitive to name the command "svnadmin
optimize". Svnadmin optimize would deltify or undeltify each
revision (as necessary). Each revision could have flags for
whether to optimize for space or speed. A post-commit hook might
run "svnadmin optimize -r HEAD".
If future optimization operations are added those could be made
part of the single command you can run nicely from a cron job,
e.g. subversion-900.0 'svnadmin optimize' might have options for
compiling usage statistics and compressing deltas older than 1
year and undeltifying revisions accessed more than 50 times in the
>>>>> "Tim" == Leeuw van der, Tim <firstname.lastname@example.org>
Tim> Except that you can explicitly undeltify certain
Tim> revisions of your choosing, if for instance it's an often
Tim> retrieved revision...
Tim> So you need another bit saying that this revision should
Tim> not be automatically deltified b/c the admin wants to
Tim> have it undeltified.
Tim> -----Original Message-----
Tim> From: Karl Chen [mailto:email@example.com]
Tim> Sent: maandag 24 november 2003 10:11
Tim> To: Subversion Development List
Tim> Subject: deltification question
> Is there a convenient way to "deltify revisions that have
> not been deltified"?
> svnadmin deltify -r1:HEAD repos
> increases the database size when run repeatedly (including
> pruning log files). (In fact, I wasn't paying attention the
> first time I ran it, so I'm not sure it EVER decreases
> If there isn't already, maybe there should be a bit in each
> revision that says whether it has already been deltified, so
> svn can skip over it quickly (and without using more space)?
> Seems to me the default interface for use in cron jobs (as
> opposed to after each commit) should only require "svnadmin
> deltify repos" to deltify anything undeltified, instead of
> -- Karl Chen 2003-11-24 00:59
Karl Chen 2003-11-24 02:32
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 24 11:44:48 2003