Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having a situation with TortoiseSVN where I am not able to trace back the file that has been move to other directory. This is the process I move and commit the file:

  1. I checkout the file locate in path_A.
  2. copy the file to path_B.
  3. delete the file in path_A.
  4. commit both path_A and path_B.

When I bring up Log Message, I only able to see the log locate in path_B but the log before it were gone. Is there a way to trace back the log for a particular file?

share|improve this question
Are you using the TortoiseSVN copy or the Windows explorer copy? – faker Mar 13 '13 at 10:37
yes. But is the implementation is different between OS? – huahsin68 Mar 13 '13 at 13:29
up vote 1 down vote accepted

I'm unsure by your comment what exactly you use to copy the file, but nevertheless:
You must use the TortoiseSVN copy/move function in order to retain the files history.

If you copy the file in any other way you are basically doing this behind SVNs back.
It cannot know that this file is actually a copy of another file.

If you use the TortoiseSVN function it tells the SVN server that FileB is a copy of FileA at revision X and it takes over its history.

If you are unsure how this is done, there is a good documentation at:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.