The docs seem pretty clear to me: svn_delta_path_driver() produces a depth- first editor traversal, where for each PATH in PATHS the portion in-and- below PATH is handled by the callback (including the open_*() or add_*() calls for PATH itself), and the portion of opening/closing the parent and ancestors of PATH is handled by svn_delta_path_driver() itself.
I have only read its docstring --- not its definition or callers --- so I might be oversimplifying things. :) ---- What context did you run into this in? Trying to revv that function? To upgrade its callers to Ev2? On Monday, November 28, 2011 4:34 PM, "Hyrum K Wright" <hyrum.wri...@wandisco.com> wrote: > In working on the Ev2 shims, I discovered svn_delta_path_driver(), a > nifty little API whose purpose I haven't totally yet discerned. It > looks to be some kind of hybridization of the editor, allowing a > caller to handle some portion of the editor drive manually, though the > documentation has enough ifs, buts, and wherefores to make me a bit > unsure. > > If I am correct, however, it would appear that this API is not > compatible with our current editor shims, which queue up all changes > made in an editor, and then play them back through the new shim. > > Any illumination by folks knowing more than I would be appreciated. > > -Hyrum > > -- > > uberSVN: Apache Subversion Made Easy > http://www.uberSVN.com/ >
