From c80994c86b53706ad850434491c1064c6f37cebd Mon Sep 17 00:00:00 2001 From: DavidD Date: Mon, 17 Apr 2023 15:27:49 +0000 Subject: [PATCH] Added a comment --- .../comment_4_9da0d19529dfb8a997ad469169e55895._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/submodules/comment_4_9da0d19529dfb8a997ad469169e55895._comment diff --git a/doc/submodules/comment_4_9da0d19529dfb8a997ad469169e55895._comment b/doc/submodules/comment_4_9da0d19529dfb8a997ad469169e55895._comment new file mode 100644 index 0000000000..8f8f517329 --- /dev/null +++ b/doc/submodules/comment_4_9da0d19529dfb8a997ad469169e55895._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="DavidD" + avatar="http://cdn.libravatar.org/avatar/9e7cced3eede4bf75fb932bfdd4f8847" + subject="comment 4" + date="2023-04-17T15:27:49Z" + content=""" +I might have this wrong, but I thought git also put things into `$repo/.git/...`? If git can figure out that the `.git` file points to the actual location of the `.git` folder (in the parent repo) than I would think that git annex can conclude this as well. Again, I don't know how the guts of git annex works, so there is possibly other considerations that I am missing. +"""]]