From fc10ac3be290982d52a15ff38ba36394693cf32e Mon Sep 17 00:00:00 2001 From: NewUser Date: Mon, 20 Nov 2023 13:17:03 +0000 Subject: [PATCH] Added a comment --- ...6_3afdea4f3705a9cfaa971ed3aa9f114c._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/git-annex-uninit/comment_6_3afdea4f3705a9cfaa971ed3aa9f114c._comment diff --git a/doc/git-annex-uninit/comment_6_3afdea4f3705a9cfaa971ed3aa9f114c._comment b/doc/git-annex-uninit/comment_6_3afdea4f3705a9cfaa971ed3aa9f114c._comment new file mode 100644 index 0000000000..d1109eb926 --- /dev/null +++ b/doc/git-annex-uninit/comment_6_3afdea4f3705a9cfaa971ed3aa9f114c._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="NewUser" + nickname="dont.post.me" + avatar="http://cdn.libravatar.org/avatar/90f59ddc341eaf9b2657422206c06901" + subject="comment 6" + date="2023-11-20T13:17:03Z" + content=""" +Thank you for the illuminating comment! + +> This is also what the error message says, btw. + + Not continuing with uninit; either delete or git annex add the file and retry. + +You’re right! I thought I only had a relative symlink pointing to the other symlink and not pointing into .git/annex/objects. It turns out that this is true for most of my symlinks but, just like you pointed out, some of them were pointing into .git/annex and the right thing to do there is to `add` them. + +Also, thank you for pointing me towards todo/bugs/forum! + +"""]] -- 2.30.2