Hi, I figured that the dump editor in libsvn_repos/dump.c unnecessarily uses a filesystem backing when it's actually not necessary; over the last week, I've been writing an editor to produce a dumpfile on-the-fly using the replay API. I plan to plug this into svnsync in future, but I'm developing it as an independent application for now. Since I plan to get the independent application merged into git.git as part of a larger project, I've had to destroy the structure and whitespace making it completely impossible to generate a diff of my work- this shouldn't actually be a problem because my dump editor already diverges from the one in dump.c significantly. When I have verified that it works, I plan to generate a nice patch series to get it merged into Subversion (and remove it from git.git in favor of just linking/ calling). I've also been discussing the design actively on the #svn-dev IRC channel, and Daniel suggested that I bring the list into the loop immediately- my current implementation is a heavy WIP, and currently just dumps actions, and property lengths corresponding to dir_prop_changed. I'd appreciate any comments/ suggestions.
http://github.com/artagnon/svn-dump-fast-export/tree/ra-svn Thanks. -- Ram p.s- Kindly CC me in all relevant emails as I'm not subscribed to this list.
