hg mv old new equivalent to mv old new hg addremove

[Uwe Brauer]

>>> "RW" == Rainer Woitok <rainer.woitok at gmail.com> writes:

   > Uwe,
   > On Saturday, 2020-07-25 19:26:36 +0200, you wrote:

   >> ...
   >> Is 
   >> 
   >> hg mv old new 
   >> equivalent to 
   >> mv old new 
   >> hg addremove

   > Superficially yes.  But if you look closer, the information is lost that
   > file "new" is not really new but rather just received a new name.

I presume hg mv is «safer» in that sense. But what information does it
preserve? 
I can't use annotate in none of these two cases, which as I understand
would be in general impossible, if I merge two files into a single one,
still I found the following email from Matt some years ago:
https://www.mercurial-scm.org/pipermail/mercurial/2012-March/042407.html 

 hg annotate -r 2519^ "set:follow(somefile)"

But this was never implemented as far as I can see
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20200726/868a6e96/attachment.p7s>