From: Joey Hess <joeyh@joeyh.name>
Date: Tue, 10 Nov 2020 15:53:45 +0000 (-0400)
Subject: comment
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~102^2~100
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=9e8eae20e2b0bf1d8b5b8d0e81d1d9e79d6113e5;p=git-annex.git

comment
---

diff --git a/doc/bugs/file_not_correctly_added/comment_10_07583ff86653cb262f84e307c2ffc797._comment b/doc/bugs/file_not_correctly_added/comment_10_07583ff86653cb262f84e307c2ffc797._comment
new file mode 100644
index 0000000000..978128448c
--- /dev/null
+++ b/doc/bugs/file_not_correctly_added/comment_10_07583ff86653cb262f84e307c2ffc797._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 10"""
+ date="2020-11-10T15:50:10Z"
+ content="""
+So was myLargeFile.CR2 in fact an annex pointer file all along?
+
+Anyway, I think it might be possible to avoid this confusing kind of
+situation. If git-annex add sees an annex pointer file or symlink, it can
+check if there's a location log file for it. Normally there always is. If
+not, that's a situation where some file from another annex is being added,
+and it can either warn, or refuse to proceed.
+
+This will only really be worth doing if git-annex smudge --clean can also
+do it, so if git add is used it does the same check.
+"""]]