[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #17 from Miklos Vajna --- I get what you say, but it goes against the whole idea described comment 2, and comment 4 already mentions how we have an OS-provided API to do this on Windows and how on Linux we manually move the

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #16 from Alex --- PS: I realize I was maybe not very clear either in my initial explanation, sorry about that... -- You are receiving this mail because: You are the assignee for the

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #15 from Alex --- (In reply to Miklos Vajna from comment #14) > I got back to this and I'm afraid 'cp -a' can't copy the creation time of > the destination document after all. > > Here is what I tried: > > 1) Save test.odt

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 Miklos Vajna changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #13 from Alex --- (In reply to Miklos Vajna from comment #4) I figured the following regarding rsync. In case the file DEST already exists, the commands $ rsync -t --inplace SOURCE DEST preserves the crtime of DEST and

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #12 from Alex --- Ah, no. I just realized that timestamps attributes are independent of extended attributes. This was a false lead, sorry. -- You are receiving this mail because: You are the assignee for the

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #11 from Alex --- I also found some additional information in this Q: https://unix.stackexchange.com/questions/118840/preserving-extended-attributes-with-cp-rsync/119980#119980 By the way, thanks for having a look into this.

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #10 from Alex --- No problem. I don't know if it can be useful but I also came across the case of rsync, which has an -X (--xattr) option to preserve extended attributes. See:

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #9 from Miklos Vajna --- Thanks for the 'cp -p' example, I'll take a look what APIs it uses. -- You are receiving this mail because: You are the assignee for the bug.___

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 Aron Budea changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #8 from Alex --- Bonus: this method might also eliminate the need to take care of hard links. :) -- You are receiving this mail because: You are the assignee for the bug.___

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #7 from Alex --- 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:

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #6 from Miklos Vajna --- We already detect the situation when the hard link count is >1 and go back to the old slow way. I just don't see a similar way for the creation time part, it seems the rest of the world just don't

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #5 from Alex --- Some additional thoughts. Reading about the g_file_set_contents() function[1] it points to the fact that changing the inode number also breaks existing hard links to the original file (wow!). I don't know

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #4 from Miklos Vajna --- Windows provides , the closest what we have is already happening on Linux, as far as I see. That's why I lean

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 --- Comment #3 from Alex --- How is it done in Windows? From the link to LWN it seems it uses the tunnel effect... is that correct? Else, couldn't it be implemented the same way in Linux? Maybe a work around in Linux (to at least

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 Miklos Vajna changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #2 from

[Libreoffice-bugs] [Bug 125401] FILESAVE: Saving a document creates a new file (new inode number) thereby messing-up with the creation time of the document

https://bugs.documentfoundation.org/show_bug.cgi?id=125401 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks|