From cf08ac583a8b52c8597e331162e90e27731dbf99 Mon Sep 17 00:00:00 2001
From: gitannexuser2021 <gitannexuser2021@web>
Date: Tue, 19 Oct 2021 22:37:45 +0000
Subject: [PATCH 1/2] Added a comment: Still seeing the issue.

---
 .../comment_1_a7a613c3fa1bee42442a446366027381._comment   | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/bugs/Host_resolution_error_on_Android_when_adding_RSync.net_repo/comment_1_a7a613c3fa1bee42442a446366027381._comment

diff --git a/doc/bugs/Host_resolution_error_on_Android_when_adding_RSync.net_repo/comment_1_a7a613c3fa1bee42442a446366027381._comment b/doc/bugs/Host_resolution_error_on_Android_when_adding_RSync.net_repo/comment_1_a7a613c3fa1bee42442a446366027381._comment
new file mode 100644
index 0000000000..71c50228ef
--- /dev/null
+++ b/doc/bugs/Host_resolution_error_on_Android_when_adding_RSync.net_repo/comment_1_a7a613c3fa1bee42442a446366027381._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="gitannexuser2021"
+ avatar="http://cdn.libravatar.org/avatar/e0d5a0aa4ca494b520a971c53865edcd"
+ subject="Still seeing the issue."
+ date="2021-10-19T22:37:44Z"
+ content="""
+I'm using termux to install git-annex on my android. When trying to add Rsync.net repo, the provided hostname cannot be resolved. Adding repo on my laptop (linux) works normally. I'm able to ping the hostname via termux successfully.
+"""]]

From 2ae821e4580ebd7671e88802a844d620b185d2e8 Mon Sep 17 00:00:00 2001
From: "asakurareiko@f3d908c71c009580228b264f63f21c7274df7476"
 <asakurareiko@web>
Date: Wed, 20 Oct 2021 14:42:33 +0000
Subject: [PATCH 2/2] Added a comment

---
 ..._276be047d18b2e20a8e3114abe3132ee._comment | 36 +++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_276be047d18b2e20a8e3114abe3132ee._comment

diff --git a/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_276be047d18b2e20a8e3114abe3132ee._comment b/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_276be047d18b2e20a8e3114abe3132ee._comment
new file mode 100644
index 0000000000..0a267591d8
--- /dev/null
+++ b/doc/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/comment_7_276be047d18b2e20a8e3114abe3132ee._comment
@@ -0,0 +1,36 @@
+[[!comment format=mdwn
+ username="asakurareiko@f3d908c71c009580228b264f63f21c7274df7476"
+ nickname="asakurareiko"
+ avatar="http://cdn.libravatar.org/avatar/a865743e357add9d15081840179ce082"
+ subject="comment 7"
+ date="2021-10-20T14:42:33Z"
+ content="""
+I tested 0f38ad9a6 with the test case below as well as with the repo I use and sqlite errors no longer occur. Adjusted branches still do not work but everything else with unlocked files seems to be ok now. Thank you Joey.
+
+Setup:
+
+```
+# on NTFS volume mounted with metadata option
+git init annex
+cd annex
+git annex init
+git config annex.addunlocked true
+git config annex.crippledfilesystem true
+echo aaa > a
+cp a b
+git annex add .
+git commit -m .
+```
+
+Test:
+
+```
+git clone annex annex2
+cd annex2
+git annex init
+git config annex.crippledfilesystem true
+git annex get .
+```
+
+
+"""]]