Can't push any more to different file-based repos with TimeStampMod enabled
Created originally on Bitbucket by wittifred (Sven Witterstein)
Context: One thing that was cool almost a decade ago was the TimeStampMod extension allowing to preserve (and essentially play around with through hg timestamp -s / -r) original file mtimes as the OS of the user creating a given data snipped I intended to track in hg recorded it on his machine.
I have a lot of (private backup) repos to push to, like
- one on the network/cloud
- one on local sdcard backup
- some on special sandbox branches. It is quite painful to visit each location (formerly just pushed to) and pull, so I would love if I could just do a couple of push-clicks in the sync dialogue.
Is: Now something changed with mercurial 3.6 which leads to tortoisehg workbench to have file-based (same work station, but different file system) pushes to other repos fail with error 255.
Expected: the timestamp mod becomes relevant, when working copy content is changed/restored or otherwise modified. Merely pushing changesets to a remote repo that otherwise accepts pushes should not be influenced/aborted - even when timestamp mod is enabled. It used to work in 3.5.x and before.
I have not much time to invesitgate but I would be accepting, if a competent dev ruled out a thg but and asked me tor report a bug within core commandline hg 3.6.
I also noted a fail for windows 7-based right-click-drag-and-drop "hg move" when handling more than >10 files or different folders (I am handling 1000s of files under hg sometimes when moving them).