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

Re: svndumpfilter --drop-empty-revs

From: Rafael Garcia-Suarez <raphel.garcia-suarez_at_hexaflux.com>
Date: 2003-08-29 15:51:51 CEST

Garrett Rooney wrote:
> Rafael Garcia-Suarez wrote:
> > The docs for svndumpfilter seem to be rather terse as of 0.28.
> > Where can I find explanations for its options ?
> >
> > I'm not sure what is the actual effect of "--drop-empty-revs".
> > This options sounds a bit too "internal" for the average svn
> > administrator...
> >
> When you use svndumpfilter to move one branch of a repository (say the
> part of the svn.collab.net repos that held rapidsvn or gsvn), you can
> either insert empty revisions for commits that occured in other parts of
> the repository (so that the revision numbers in the new repository are
> the same as those in the old one, so if people mentioned specific
> revisions in bug reports, or emails, or whatever they don't become
> invalid), or you can rip out empty revisions and allow the revision
> numbers to change if you are bothered by the idea of a lot of empty
> revisions.

Yes indeed ; what I meant is that, from the user point of view,
the sole option "--renumber-revs" seems sufficient. I don't see
the point of having "--renumber-revs" _and_ "--drop-empty-revs",
and that's why I'm asking if there's something I've missed
about those options.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 1 00:27:18 2003

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.