On 03/08/2011 05:11 AM, Avalon wrote: > I would appreciate the feature since it would also be very useful for tools > like WebSVN. > How realistic would it be to get it implemented in the near future? > While having good programming skill i have never compiled subversion myself. > But if any help is needed e.g. for testing i would be happy to support.
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). 2. Consider deletion events as "interesting history points" when displaying the revisions logs for a given path. This is a bit more controversial, as our revision log display is driven wholly by the DAG structure of the version filesystem, and a deletion event doesn't leave a trace on the part of the DAG related to the deleted thing. Deletion is an event which occurs on the parent directory of the deleted thing only. That said, I recognize the value in showing *something* to users so that they can tell the difference between "Nothing new has happened to PATH lately" and "...that's because PATH has been deleted". -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand