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

Re: Svndumpfilter inconsistent behaviour in subversion 1.5

From: Murli Varadachari <mvaradachari_at_facebook.com>
Date: Tue, 27 May 2008 11:11:45 -0700

Sorry about ‹ thought I was starting a new thread.

Chers
murli

On 5/27/08 10:16 AM, "Blair Zajac" <blair_at_orcaware.com> wrote:

> Hi Murli,
>
> Not related to your post, but please don't reply to a Subversion question to
> start a new thread, as it still is associated to the original question. So
> people may miss your question if they don't read the original question. Read
> this thread for more info.
>
> http://subversion.tigris.org/mailing-list-guidelines.html#fresh-post
>
> Regards,
> Blair
>
> Murli Varadachari wrote:
>> >
>> > I tried using svndumpfilter to split an existing repository. My intention
>> > was to keep the filtered revisions visible [ but empty ] and in the process
>> > retain the original revision numbers across the split repositories.
>> >
>> > I used the following commands
>> >
>> > svndumpfilter --drop-empty-revs ......
>> >
>> > I chose *not* to use "--renumber-revs" option.
>> >
>> > However after a dump and load into a new repository the revision numbers
>> > were re-arranged. I thought the "renumber-revs" was an explicit option --
>> it
>> > appears it is the default.
>> >
>> > Is there any way to prevent this [ or is this a bug}
>> >
>> > Cheers
>> > murli
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>> > For additional commands, e-mail: users-help_at_subversion.tigris.org
>> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
Received on 2008-05-27 20:12:25 CEST

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.