From 3d51f866d30865bd888eb03a1a6b51af0755d0c1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 20 Sep 2022 14:02:09 -0400 Subject: [PATCH] comment --- ...4_9a3f50f1b8cfd1cc0da83937a36e1369._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/does_not_preserve_timestamps/comment_14_9a3f50f1b8cfd1cc0da83937a36e1369._comment diff --git a/doc/todo/does_not_preserve_timestamps/comment_14_9a3f50f1b8cfd1cc0da83937a36e1369._comment b/doc/todo/does_not_preserve_timestamps/comment_14_9a3f50f1b8cfd1cc0da83937a36e1369._comment new file mode 100644 index 0000000000..a48afdc01d --- /dev/null +++ b/doc/todo/does_not_preserve_timestamps/comment_14_9a3f50f1b8cfd1cc0da83937a36e1369._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2022-09-20T17:55:45Z" + content=""" +Note that `git-annex add` does preserve the timestamp of the file +while adding it to the annex. Much the same as a file's timestamp is +the same after `git add` as it was before running that command. +When `git-annex add` replaces a file with a symlink, it even makes the +symlink's timestamp be the same as the original file. + +What git-annex does not do is try to store the timestamp in git and arrange +for clones that receive the file to get the same timestamp. There are lots +of things like this that someone *might* want git to preserve, but git +doesn't, and it's out of scope for git-annex to try to work around git's +limitations in these areas. Plenty of room for other tools that add +git tracked timestamps, etc. Many such tools exist. +"""]]