From 39fed072892a7c36a2c179c933fc6c3f993d54ad Mon Sep 17 00:00:00 2001 From: kdm9 Date: Mon, 4 Dec 2023 10:09:16 +0000 Subject: [PATCH] Added a comment --- ...mment_1_b2ecb8b60603929bae91c3007817585f._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/annex.largefile_not_working/comment_1_b2ecb8b60603929bae91c3007817585f._comment diff --git a/doc/forum/annex.largefile_not_working/comment_1_b2ecb8b60603929bae91c3007817585f._comment b/doc/forum/annex.largefile_not_working/comment_1_b2ecb8b60603929bae91c3007817585f._comment new file mode 100644 index 0000000000..200a8dcdce --- /dev/null +++ b/doc/forum/annex.largefile_not_working/comment_1_b2ecb8b60603929bae91c3007817585f._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="kdm9" + avatar="http://cdn.libravatar.org/avatar/b7b736335a0e9944a8169a582eb4c43d" + subject="comment 1" + date="2023-12-04T10:09:15Z" + content=""" +I think this is intended behavior when adding with `git add`, or at least it's what I've seen for long enough for me to have forgotten if it ever was different. `git annex add` will create symlinks, as will `git add && git annex lock`. + +If this was actually a small file, you wouldn't see it hashed & copied under .git/annex/objects. You should also see in git log that the change is an addition of some git annex key, not a git blob diff as would be the case for a small file. + +NB: I'm just another user, @joey please correct me if this is wrong +"""]]