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

BUG: "Show Log" always shows log of HEAD instead of the file I click on

From: Oliver Meyer <Oliver.Meyer_at_dsa.de>
Date: Mon, 29 Jun 2015 10:32:57 -0700 (PDT)


If I update a directory to a certain revision, the log that "Show Log" displays is wrong. TortoiseSVN shows the log of the HEAD version of the file, while the file I enquire the log of is in a different revision and thus has a different log.

The log that "svn log filename" shows and the log that TortoiseSVN for the same file (on my hard disc) shows are different. I expect the logs to be the same.

I experience the problem with 1.7.x but checked with 1.8.11. The problem is still there.

What I do:
I create multiple versions of a file in folder SRC.

From time to time I "svn copy" the file from SRC into another version controlled folder RELEASED, to mark the file as being released.

I eventually update my local copy of RELEASED to a previous (non HEAD) revision.

If I look at the log of the file with Tortoise SVN, I do see revisions that are larger than the revision of the file itself. Thus, I do see change messages, for changes that have not happend to the file.
If I look at the log using "svn log" I do see just the history and not the future.

I will attach the following illustration as a file, because I do not know, if the alignments will work here.

REV SRC RELEASED log message
  1 file.txt did change A
  2 file.txt did change B
  3 file.txt -> file.txt released revision 2 of file.txt
  4 file.txt did change C
  5 file.txt -> file.txt released revision 4 of file.txt
I checkout RELEASED.
I svn update RELEASED to rev. 3
I right click of file.txt inside of RELEASED and call "Show Log" with TortoiseSVN. I get:
   5 released revision 4 of file.txt
   4 did change C
   2 did change B
   1 did change A
 If I use svn log file.txt I get the correct log of RELEASE/file.txt_at_3
   3 released revision 2 of file.txt
   2 did change B
   1 did change A
The problem does not bother me too much and there is a workaround (use the command line), but I believe that no one has thought of this use case, so maybe you might see it as a little mind teaser. Or, can someone explain to me, why tortoiseSVN's change log should be considered correct in this case?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2015-06-29 19:43:40 CEST

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

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