<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125401#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125401">bug 125401</a> from <a class="email" href="mailto:alex.dwd@gmail.com" title="Alex <alex.dwd@gmail.com>"> Alex</a> <pre>Ah. Good that the hard link problem is taken care of. :) Not sure that the rest of the world just don't care, see for instance this recent thread here: <a href="https://www.linuxquestions.org/questions/linux-newbie-8/how-do-i-preserve-crtime-creation-birth-time-when-copying-from-windows-ntfs-to-linux-ext4-4175625229/">https://www.linuxquestions.org/questions/linux-newbie-8/how-do-i-preserve-crtime-creation-birth-time-when-copying-from-windows-ntfs-to-linux-ext4-4175625229/</a> I admit it is a different case-scenario so I don't try to lean heavily on it, but the thread is still an interesting read. Reflecting on this read, I just noticed that for the file replacement, instead of doing: $ mv SOURCE DEST (which preserves neither the creation time nor the modification time) one could do: $ cp -p SOURCE DEST (which preserve both). Wouldn't it be simple/easy to implement?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>