Don't know if this should be a new topic or not, it's related based on based on "creation date".
When WinSCP copies files, it can & does sync the "modified" date, but the "creation" date is changed to the time the file was transferred/copied. I know this is "standard behavior" for Windows (it loses timestamps all the time when copying), but it's wrong.
Can I ask for a "no, really, preserve EVERYTHING" option?
I want to copy/sync files between computers & not lose anything. I mean anything: Not lose timestamps due to "DST" issues. Not lose the "creation" date. Not lose anything. I mean for file AND dirs. Not sure how "Dropbox" works, but if it syncs all timestamps, then like that...otherwise, WinSCP can be the first to "do it right".
Also, with Win7/Vista...there are like a million "other" date columns you can display, not sure if you can set/sync those too, but that would be good.
If you don't wanna write this yourself (although that would probably be easier), can I ask for the option of having "pre-copy" & "post-copy" commands?
Some command I can run on the local &/or remote side before & after the copy. Then I could write a program to retrieve the timestamps & then set them on the other side. I'd need a way to transfer the output of the command from one side to the other tho (temp file or pipe).
Pre-copy command: timestamps-get.exe $file-or-dir-being-copied
[ ] Dest-side command [x] Capture stdout
Post-copy command: timestamps-set.exe
[x] Dest-side command [x] Send Pre-copy command's stdout to stdin
...I hope that example is clear enough. Specify a program that gets timestamps from source side of copy, transfer info over stdout/stdin to other side, then specify a program that sets timestamps on dest side of copy.
Actually, pre/post-copy commands would be useful, even if you did implement full timestamp preservation internally.