comment

diff --git a/doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_8_0a7f24a4567ff934cee37a4c0224f000._comment b/doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_8_0a7f24a4567ff934cee37a4c0224f000._comment
new file mode 100644 (file)
index 0000000..55813f9
--- /dev/null
+++ b/doc/bugs/adb_creates_empty_commits_on_import__47__sync/comment_8_0a7f24a4567ff934cee37a4c0224f000._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 8"""
+ date="2022-01-31T16:26:55Z"
+ content="""
+Well that message suggests that the CID of the file appears to have
+changed. But I investigated the changed CID theory back in comment #4 and
+could not get it to produce an empty commit.
+
+The file being not annexed might be a clue.
+
+If it happens with a symlink, that would certianly be a clue. But
+git-annex avoids exporting symlinks to special remotes now, so it would be
+worth upgrading to the most recent release to avoid the old behavior with
+them.
+"""]]