From c60b66d442eb768491369d770ba6fc54363f0d09 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 10 May 2021 12:44:53 -0400 Subject: [PATCH] comment --- ...comment_4_8d1ba01f4e25606b960023eab38ec483._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/one-off_unlocked_annex_files_that_go_against_large/comment_4_8d1ba01f4e25606b960023eab38ec483._comment diff --git a/doc/forum/one-off_unlocked_annex_files_that_go_against_large/comment_4_8d1ba01f4e25606b960023eab38ec483._comment b/doc/forum/one-off_unlocked_annex_files_that_go_against_large/comment_4_8d1ba01f4e25606b960023eab38ec483._comment new file mode 100644 index 0000000000..cd3d8215c4 --- /dev/null +++ b/doc/forum/one-off_unlocked_annex_files_that_go_against_large/comment_4_8d1ba01f4e25606b960023eab38ec483._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2021-05-10T16:43:00Z" + content=""" +Maybe the solution would be for `git annex add`, whenever it decides to +add a file to git (due to --force-small or largefiles config), to drop the +inode out of the keys database? I think that would make all of the cases +described so far work. +"""]] -- 2.30.2