Firstly, let me thank everyone for their help. I was "hoping / wishing" that here was some simple command line instruction(s), that I simply didn't know about, that would do the job for me. It would appear, not in the way I had hoped.
Mark Cooke suggested that I use a hook script to maintain the log every update, that way all I ever had to do was grep and not the log creation too. Which is an excellent idea, and seems to be inline with the earlier suggestion of Stefan's of using "svnsearch" or "fisheye" for the task. It was more a case of working out if I "could" do what I want internally within subversion, or whether Google was correct and I had to use one of the processes that have now been mentioned here. Slightly different but I only just found out that you can use svn merge to obtain a list of changes that an svn update will do to your working copy. svn merge --dry-run -r BASE:HEAD . which in effect is a svn update with a --dry-run switch. So I just wanted to make sure something like that didn't already exist for me to find out a deleted revision / path of a long lost file. Thank you everyone for your considered responses - I do appreciate the time you've taken to help me out. Gavin "Beau" Baumanis On 19/04/2011, at 2:21 AM, Henrik Sundberg wrote: > On Wed, Apr 13, 2011 at 3:27 AM, Gavin "Beau" Baumanis > <gavin.bauma...@palcare.com.au> wrote: >> Create a file with svn log >> (svn log --verbose > svn.log) >> Then grep / search the log for the file you're after. >> >> Is there not a more convenient way to do this? > > Have you seen ViewVC? > /$
