Reputation: 15122
The following is the result of svn log -v and it stops in the revision of files/dirs moving. How can I get the full tracked log?
svn log -v
r3171 | drake | 2010-08-16 15:04:49 +0800 (Mon, 16 Aug 2010) | 1 line
Changed paths:
D /lib/python2.5/dgGetFileSequence.py
D /lib/python2.5/dgHumanSort.py
D /lib/python2.5/dgconfig.py
D /lib/python2.5/dgdata.py
D /lib/python2.5/dgtools.py
A /python/dgtools/dgGetFileSequence.py (from /lib/python2.5/dgGetFileSequence.py:3170)
A /python/dgtools/dgHumanSort.py (from /lib/python2.5/dgHumanSort.py:3170)
A /python/dgtools/dgconfig.py (from /lib/python2.5/dgconfig.py:3170)
A /python/dgtools/dgdata.py (from /lib/python2.5/dgdata.py:3170)
A /python/dgtools/dgtools.py (from /lib/python2.5/dgtools.py:3170)
Upvotes: 5
Views: 4099
Reputation: 43575
svn log
will give you the full log even across renames/moves/copies. Only if you specify --stop-on-copy
it will stop on renames/moves/copies.
If it doesn't cross those for you, then you have not renamed/moved/copied your files with the appropriate svn command (svn mv
, svn cp
) but done so directly without telling svn about it. In that case, those files are not related and you've 'lost' the history. You have to show the log for the original file manually.
Upvotes: 3