On Thu, 17 Aug 2006, Magnus Naeslund(k) wrote:
> C. Michael Pilato wrote:
>>
>> I'm not aware of such a bug.
>>
>> There are a couple of things you could do to facilitate someone here helping
>> to debug the situation:
>>
>> * Provide the output of 'svn log -v -q' from your original repository.
>>
>> * Provide the dumpfile, or at least maybe slosh it through grep so we
>> can see the revisions, and the paths and operations in those revisions:
>>
>> $ cat dumpfile | \
>> grep -E '(Revision-number:|Node-path:|Node-action:|Node-copyfrom-)'
>>
>
> I'll see if I can do this, the problem is that I work for a bank, and the bank has strict policys about source code.
> I definately cannot provide the dump file, that's for sure, but I'll see about the logs and/or filtrated dumpfile thing.
Maybe svndumptool.py can help here (though it only works for dump files
without deltas).
It can show a log (almost identical to svn log) of the contents of the
dumpfile, and some of the other commands may also be useful.
And if you want to tweak a dumpfile you can use the svndump classes
directly.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 17 21:07:10 2006