On Wed, Nov 10, 2010 at 11:48 AM, Les Mikesell <lesmikes...@gmail.com> wrote: > If something is deleted and recreated there is no history connecting them > even if those things have the same name, so what you are asking for doesn't > really exist. Maybe you could 'svn log -v' a parent or the top level of the > repo and parse out the deletes/adds you want to see.
Running `svn log` on the top level of the repository is one of the solutions proposed to my stackoverflow question. However, this is extremely inefficient for large repositories with long histories. You can imagine implementing a visualization tool that lets you zero-in on a specific path and see what has lived there at any point between revision 1 and HEAD. It would be absurd if the command to generate a view of this one path took as long as the command to view the history of the entire repository. I'm saying that this is a valid use-case that the svn cli does not currently satisfy, but one which it could easily satisfy because it stores all the necessary information. As a client, this should be as easy for me as something like this: `svn log -v --path ...` where the --path option would tell svn to stick to that path, not to the pegged revision currently at that path. -Klaus
