diff --git a/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment b/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment
new file mode 100644
index 0000000000..c234527fac
--- /dev/null
+++ b/doc/sync/comment_29_161c5d3f693de45070e037d27ee7e8aa._comment
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb"
+ nickname="talmukoydu"
+ avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed"
+ subject="`git annex sync` not automatically syncing gcrypt remotes using relative paths"
+ date="2023-03-19T19:20:44Z"
+ content="""
+@joey Is this a bug or am I missing something?
+
+Notes:
+
+* I am using the latest git-remote-gcrypt, version 1.5
+
+Flow 1
+
+* `git remote add test gcrypt::rsync://user@user.rsync.net:relative/path/to/repo`
+* `git annex sync` -> DOES NOT SYNC to test remote
+* Nothing has been synced so I CANNOT successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo`
+* `git push test git-annex master`
+* I can successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo`
+
+Flow 2
+
+* `git remote add test gcrypt::rsync://user@user.rsync.net/full/path/to/repo`
+* `git annex sync` -> DOES SYNC to test remote
+* I can successfully clone from the test remote with `git clone gcrypt::rsync://user@user.rsync.net:relative/path/to/repo`
+"""]]
diff --git a/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment b/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment
new file mode 100644
index 0000000000..41a455d79d
--- /dev/null
+++ b/doc/sync/comment_30_f75f5957dbd0f6fd7b2d7291f06e7489._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="talmukoydu@ab15521191b4d02584d003f3f211d90f575d5ebb"
+ nickname="talmukoydu"
+ avatar="http://cdn.libravatar.org/avatar/965ffeb49ec136674054e50928ddb2ed"
+ subject="RE: `git annex sync` not automatically syncing gcrypt remotes using relative paths"
+ date="2023-03-19T19:27:46Z"
+ content="""
+@joey definitely seems like a bug. I am able to easily verify by changing the remote url back and forth in the .git/config and then running git annex sync. If the relative url is used git annex sync does not sync to that remote.
+"""]]