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

RE: SVN Blame doesn't work well with moved files

From: Craig McQueen <craig.mcqueen_at_beamcommunications.com>
Date: Thu, 31 Mar 2011 16:39:36 -0700

From: Stefan Küng
> On 22.03.2011 01:04, Craig McQueen wrote:
> > Blame is a very useful tool, though I’m having trouble using it on
> files
> > that have been moved.
> >
> > I have a working copy that is updated to an old revision of a
> > repository. It contains a file that has subsequently been moved. If I
> > try to do a “blame” on that file in that working copy (revisions 1 to
> > HEAD), I get an error message “File not found: revision xxxx, path
> > ‘/etc/etc/movedfile.c’. (I don’t want to update the working copy to
> > HEAD, because I’m interested more in the file’s older history,
> excluding
> > all that’s happened to it after it was renamed.)
> >
> > Perhaps by saying up to HEAD, that implies that the file must still
> be
> > at the same path in HEAD. However, what I wish for is for Blame to
> look
> > at the file’s history pegged at the path and revision that the
> working
> > copy revision points to, and going as far forward as possible.
> >
> > If the above is too hard, it would also be nice if the “Revision” box
> > was pre-loaded with the revision number of that working copy.
> Done in r21039.

Hello, I've tried this in release 1.6.15, Build 21041, and it doesn't seem to behave any differently than before. Am I misunderstanding something?

Craig McQueen


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-01 01:57:14 CEST

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