From 1e18df9c3a9f81f7c0a1c03c095fe4fa4a6ec6b6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 11 Nov 2024 14:32:44 -0400 Subject: [PATCH] response --- ...ment_1_c853700b67cc30ac3f6a9796e182b0c9._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/keeps_adding_to_git_even_though_largerthan__61__/comment_1_c853700b67cc30ac3f6a9796e182b0c9._comment diff --git a/doc/bugs/keeps_adding_to_git_even_though_largerthan__61__/comment_1_c853700b67cc30ac3f6a9796e182b0c9._comment b/doc/bugs/keeps_adding_to_git_even_though_largerthan__61__/comment_1_c853700b67cc30ac3f6a9796e182b0c9._comment new file mode 100644 index 0000000000..a0a1c26bbc --- /dev/null +++ b/doc/bugs/keeps_adding_to_git_even_though_largerthan__61__/comment_1_c853700b67cc30ac3f6a9796e182b0c9._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2024-11-11T18:22:11Z" + content=""" +I don't see how that could happen unless you still had an annex.largefiles +config somewhere. But --force-large would surely bypass +all configs and make it be added as a large file. + +The places you could have annex.largefiles set that you didn't show are in +git config, and in git-annex config. My guess is it was in git config, +since that place to set it does override any gitattributes settings. +"""]]