comment

diff --git a/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_2_0c064717d0b85ff4b9df1bada7c6e7ad._comment b/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_2_0c064717d0b85ff4b9df1bada7c6e7ad._comment
new file mode 100644 (file)
index 0000000..6010c0a
--- /dev/null
+++ b/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_2_0c064717d0b85ff4b9df1bada7c6e7ad._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2022-05-09T15:13:39Z"
+ content="""
+It might be worth preventing `git-annex init` when in an existing, already
+initalized repo from entering an adjusted branch. But re-running `git-annex
+init` generally re-does initialization, except for generating a new UUID
+and description. If a repo has been moved to a crippled filesystem,
+I think it would be reasonable for a user to expect re-running git-annex
+init will react to that. (Which can also involve setting annex.pidlock or
+disabling annex.sshcaching.)
+"""]]