From 10417bf8f61a92394560cf903c0834d81e33ae74 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 10 Nov 2015 15:38:33 -0400 Subject: [PATCH] comment --- ..._ab24dacf101a1a7e33e5976f72f6fe05._comment | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_2_ab24dacf101a1a7e33e5976f72f6fe05._comment diff --git a/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_2_ab24dacf101a1a7e33e5976f72f6fe05._comment b/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_2_ab24dacf101a1a7e33e5976f72f6fe05._comment new file mode 100644 index 0000000000..6b4cdd13c2 --- /dev/null +++ b/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_2_ab24dacf101a1a7e33e5976f72f6fe05._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-11-10T19:31:18Z" + content=""" +git annex status doesn't checksum files, so it can't be the sha executables +in PATH. + +Instead, git-annex status, when in a direct mode repository like on +windows, checks the recorded timestamps etc of the files to determine if +they're modified. + +I suppose one possibility is a time zone change or DST change. Did you +recently "fall back" from DST in your location? + +Due to the braindead way Windows deals with timezone changes, +the timestamps of files appear to *change* when the timezone has changed. +git-annex tries to detect this situation and offset to get back a stable +timestamp that can be used to detect file modifications, but I can't say +that I've tested this situation very carefully, beyond the one very painful +day implementing that workaround. + +Anyway, running `git annex sync` may result in it noticing that nothing has +actually changed and get the status display to work better. +"""]]