Please read carefully what I wrote:
If I update a file in a range where the old file exists (100-200) I would
expect a log history on this old file (and why not on the new file)
but I got the history on the new file ONLY...as if the old file did not
exists. This is not consistent with the (old) local file I have in my
I don't know exactly what svn command are sent by TSVN, but there is no
svn copy to do for running the bug.
Dave Lawrence <dlawrence_at_ad-holdings.co.uk>
Envoyé par : news <news_at_ger.gmane.org>
Veuillez répondre à
Re: log history for re-created files
> I am new on this list and hope this is the right place to report a bug !
> Here the issue I noticed with TortoiseSVN:
> Let say you add a file at revision 100, you delete it with Tortoise at
> revision 200 and you re create (add+commit) it (a new file with the same
> name) at revision 300.
> If you request a chekout ou update with revision in 100-200 range, the
> 'show log' window on the file reports only changes after build 300, but
> never in 100-200 range as you may expect !
That's expected. The new file didn't have any history before rev 300.
> Note that a 'show log' on the parent directory shows the all history for
> that file.
No, show log on the parent directory shows all the history for that
directory, which includes the history of the old file and the new file.
If the new file does actually have history from the old file, then you
could do something like
svn rm my_file
svn cp http://my_repo/some_path/my_file@199 ./my_file
svn ci my_file -m"Replacing history-less file with file copied from rev
but.. sorry I don't know exactly how to do that sort of thing in TSVN.
Maybe the "copy to working copy" in the repo-browser is the feature you
want here (you can view an "old" revision of the repo to get a view of
the old file).
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-11 14:34:52 CEST