Re: non-existent revision after dump + svndumpfilter

"Gerald Richter" <richter@ecos.de> writes:

> Hi,
>
> thanks for the feedback
> >
> > Did you run svndumpfilter with the --drop-empty-revs option? If you
> > want to preserve those working copies, *don't do that*. If you drop
> > empty revisions, there's no way you'll get all those working copies
> > synchronized again.
>
> If have tried with and without --drop-empty-revs . In both cases the
> resulting repsitory which I get after the svnadmin load has viewer revisions
> then the original one and svn up fails, because the working copy is at an to
> high revision number.

Hmm... that's inconsistent with my understanding (and testing) of how
svndumpfilter works.

Here's a different question: If you run without --drop-empty-revs,
and then do:

    $ grep 'Revision-number: ' orig-dumpfile | wc -l
    $ grep 'Revision-number: ' filtered-dumpfile | wc -l

Do you get matching values for the number of revisions in each
dumpfile?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 18:08:57 2004