[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] RE: SPAM-LOW: Re: [TSVN] List of minor issues/requests

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-09-29 18:11:43 CEST

Eric J. Smith wrote:

> Hrmm... I see what you mean, but I thought in SVN 1.1 that you could follow
> renames through history? I guess you would have to follow them forward in

It does. But the 'starting' revision must match, i.e. if you give the
'svn log' command a path to show the log for, that one must exist. If it
then sees that the file/folder got renamed, it will follow the rename.
But there's _no_ way Subversion could do the following:

svn log path/to/file_old -rHEAD

when /path/to/file_old got renamed in e.g. revision 100 to

> this case to see what the current file name is. Would that be possible? If
> not, I'd be happy just having it work on non-renamed files for now. Maybe
> you could have the context menu and when it's clicked you check to see if
> the file is still in the HEAD revision as the same name and, if it is, you
> show the log and if it isn't you display a message saying that the feature
> isn't supported on renamed files. What do you think?

That would be a _huge_ amount of work to do, and it also would take a
very long time to actually execute that function (a big for(){} loop
with many, many string comparisons in it). Also, in the log you don't
get the "copy" information in a way that is really parseable...


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 29 19:21:21 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.