Hi,
I managed to reproduce it, you need branches as well.
So, start with a trunk where you have a single file1.txt with some text in it
Create a branch b1
Checkout b1
Add a file file2.txt (with some text inside) on b1
Modify file1.txt on b1
Commit to b1 (REVISION X)
Checkout trunk
Merge b1 to trunk's working copy
Commit the merge (REVISION Y)
Now your working copy should contain file1.txt and file2.txt
Right click on file2.txt -> Blame
You can now see that for the lines of file2.txt TortoiseBlame displays revision X
Right click on any revision X, show Log
Now, if the "
Show only affected paths" option is enabled, then you can't see any path because at revision X the path was /b1.
Keep in mind that the blame option was triggered on a trunk working copy. Therefore, it is expected that the revisions displayed in the TortoiseBlame window
correspond to trunk revisions.
Expected behaviour:
- in the Blame Window the lines of file2.txt correspond to revision Y, the revision of b1's merge to trunk