Yeah, I think it is a good idea to have transfer time. Thank you!

Note that on the lastest HEAD version, soon to be packaged, the date is show at the start and completion of the backup, like this:

root@cumin1001:~/transferpy$ mkdir ~/test; PYTHONPATH=. python3 transferpy/transfer.py --port=3000 --no-checksum cumin1001.eqiad.wmnet:/home/jynus/transferpy/transferpy/ cumin1001.eqiad.wmnet:/home/jynus/test
2020-07-22 07:49:29  INFO: About to transfer /home/jynus/transferpy/transferpy from cumin1001.eqiad.wmnet to ['cumin1001.eqiad.wmnet']:['/home/jynus/test'] (159274 bytes)
2020-07-22 07:49:36  INFO: 159274 bytes correctly transferred from cumin1001.eqiad.wmnet to cumin1001.eqiad.wmnet

With the timestamps it is easy to know the transfer time. However, it will be less meaningful once the concurrent transfers get merged.

While this is a reasonable feature request, I think it is of a lower priority, and given we are on the last development week (almost) we should focus first on polishing and completing ongoing work.

Yeah, it is something with very low priority (as stated at T258559#6325133). Having both timestamps is indeed useful

Sounds good to me. And yeah, I am currently concentrating on the Gerrit comments and documentation. Thank you!