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

Re: svndumptool 0.4.0

From: Martin Furter <mf_at_rola.ch>
Date: 2007-04-12 00:47:41 CEST

On Wed, 11 Apr 2007, Max Bowsher wrote:

> Martin Furter wrote:
>>
>> Hello
>>
>> Today svndumptool 0.4.0 has been released with many new features and
>> bugfixes. The biggest feature since 0.3 is probably that it works with
>> cvs2svn created dumps now (though better is to fix them first using the
>> new command cvs2svnfix).
>
> Hmm?
>
> Wouldn't better still be to fix cvs2svn?

I looked into that a while ago but it seemed not easy to get that info.

> Oh. So, I just found the README.txt....
> [[[
>> Fixes a cvs2svn created dumpfile. Some (all?) versions of cvs2svn do not
>> create 100% valid dumpfiles according to subversions specification of the
>> dumpfile format. It omits the node kind for copied nodes. This command
>> repairs those nodes.
> ]]]
>
> Well, I'm inclined to alter the specification to state the Node-kind is
> irrelevant, and should be omitted on write, and ignored on read, for a
> copied node other than in the case of "Node-action: replace", in which
> case the Node-kind specifies the kind of the *new* node, which may be
> different from the copyfrom node.

I prefer it the way it is.

1. The node-kind is useful info for checking dump files and it's hard to
recreate (needs a lot of RAM and CPU time).

2. There's a bug in "svnadmin load": It doesn't check the node-kind in
some cases. This seems to violate the specification :P

At least if this is changed it requires a new version number for the
format of the dump file.

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 12 00:48:09 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.