From f6933c95cfdd48b3df789d226f42dd06fd899c4e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 16 Apr 2021 13:54:50 -0400 Subject: [PATCH] comment --- ...ent_3_80bf2c40cf8204c81fd0164fc2a08021._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_3_80bf2c40cf8204c81fd0164fc2a08021._comment diff --git a/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_3_80bf2c40cf8204c81fd0164fc2a08021._comment b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_3_80bf2c40cf8204c81fd0164fc2a08021._comment new file mode 100644 index 0000000000..5570a965de --- /dev/null +++ b/doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_3_80bf2c40cf8204c81fd0164fc2a08021._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-04-16T17:49:18Z" + content=""" +See also: + +Which needs the same information. + +Occurs to me one way to make sure git-annex has the information up-to-date +would be to stat the index file, and if it's changed since last time, +use `git ls-files --cached` to find all annexed files and update the keys +database. But this could be quite slow. +"""]] -- 2.30.2