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

Re: [svn 1.3.1] Revision Number changes on import via "svnadmin load"

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-01-27 22:48:41 CET

On Jan 27, 2007, at 12:16, Danny van Heumen wrote:

> Jeff Smith wrote:
>> It seems I've had the opposite problem. I tried to 'compact'
>> unused revision numbers after removing some paths from the
>> repository using svndumpfilter, but it keeps these empty revisions
>> as placeholders.
> That is intended.
> Having large files in your repository costs a lot of space and this
> space simply can't be won back unless you rebuild your repositoy
> without the files in it (like with dumping and loading a dumpfile).
> Subversion has revision numbers in abundance and it actually
> *tries* to keep the same revision for every commit because you
> could have used these numbers in log messages and such. (You
> wouldn't want a log message to say: Fixing a bug that occurred in
> r854 while you only have 700 revisions :-P.)
> I don't think it's going to be easy to "recycle" those wasted
> numbers. And I also think you shouldn't want to...

"svndumpfilter exclude" has some options which may be of interest, in
particular --renumber-revs and --drop-empty-revs:

$ svndumpfilter help exclude
exclude: Filter out nodes with given prefixes from dumpstream.
usage: svndumpfilter exclude PATH_PREFIX...

Valid options:
   --drop-empty-revs : Remove revisions emptied by filtering.
   --renumber-revs : Renumber revisions left after filtering.
   --preserve-revprops : Don't filter revision properties.
   --quiet : Do not display filtering statistics.

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jan 27 22:49:40 2007

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.