From efdcf0872a613ff2844511e6641f56082c9b8781 Mon Sep 17 00:00:00 2001 From: codelix Date: Thu, 21 May 2020 19:11:01 +0000 Subject: [PATCH] Added a comment --- ...omment_39_eee1859e679fca35d1c62b89e5bd0435._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_39_eee1859e679fca35d1c62b89e5bd0435._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_39_eee1859e679fca35d1c62b89e5bd0435._comment b/doc/forum/lets_discuss_git_add_behavior/comment_39_eee1859e679fca35d1c62b89e5bd0435._comment new file mode 100644 index 0000000000..5a1feb024a --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_39_eee1859e679fca35d1c62b89e5bd0435._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="codelix" + avatar="http://cdn.libravatar.org/avatar/667ff4d0387694f28236639bab0faf2c" + subject="comment 39" + date="2020-05-21T19:11:01Z" + content=""" +Sorry `largefiles` already sort of does this. My main hang up might just be the name, it's not intuitive what all side effects it'll have. Having it called something explicit like `addtoannex` will probably make it super clear to me. + +Also what is the current default value of `annex.gitaddtoannex`? And how does this interact with largefiles as it is now? +"""]]