From 9a78444d368c712ba88c9334043fd1e54fe503c4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 19 Apr 2022 12:08:12 -0400 Subject: [PATCH] comment --- ...nt_14_cd71d1c6e69a9fc7feadf9aa6a39c406._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/tips/largefiles/comment_14_cd71d1c6e69a9fc7feadf9aa6a39c406._comment diff --git a/doc/tips/largefiles/comment_14_cd71d1c6e69a9fc7feadf9aa6a39c406._comment b/doc/tips/largefiles/comment_14_cd71d1c6e69a9fc7feadf9aa6a39c406._comment new file mode 100644 index 0000000000..b40aff5619 --- /dev/null +++ b/doc/tips/largefiles/comment_14_cd71d1c6e69a9fc7feadf9aa6a39c406._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2022-04-19T16:03:49Z" + content=""" +@lh two possibilities are: + +1. When `git add` is run, git-annex does some additional checks to detect + things like a file that was checked into git before but has been + renamed, and will avoid annexing such a file even when annex.largefiles + says to. +2. Perhaps `git add` is finding some other git-annex + version that behaves differently. Seems unlikely, but possible. +"""]]