On Thu, May 19, 2011 at 4:18 PM, Avalon <third-cha...@gmx.de> wrote: > I wanted to take a closer look into implementing this feature and have built > the current SVN trunk. > I have looked through the code and now i have a rough understanding how the > log information is collected. > >> There are now two different issues brought up in these thread: >> >> 1. For 'svn log -rX:Y PATH@PEG, where Y> PEG, don't croak when PATH@Y >> doesn't exist. Instead, automatically substitute for Y the last revision >> in >> which PATH@THAT-REV *did* exist, and continue the operation. I believe >> this >> is something that we can reasonably achieve without too much trouble and, >> more importantly, in a client-side change (which helps with client/server >> compatibility). > > As far as i know the history is always collected from youngest to oldest > revision (not the other way around). > Your suggestion to modify Y to the latest revision where PATH@PEG still > exists looks like the easiest approach. > But i could not yet figure out how to perform this operation. > > Could you give me an advice how this could be realized or point me to some > other code area where a similar "forward" traversal/search is performed? > May be with some hints i can carry on with this by myself. > > Dirk
Hi Dirk, This might help: http://svn.haxx.se/dev/archive-2011-04/0215.shtml Paul
