followup

diff --git a/doc/bugs/multiple_records_in_remote.log_for_the_same_remote.mdwn b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote.mdwn
index a19b80b89e386b5f00c94b272b4b6f06c8d764ff..d7682da4137b143c99378b587d5ce76896680d60 100644 (file)
--- a/doc/bugs/multiple_records_in_remote.log_for_the_same_remote.mdwn
+++ b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote.mdwn
@@ -70,3 +70,4 @@ ATM 10.20240430+git26-g5f61667f27-1~ndall+1 but I guess it is unrelated.
 
 [[!meta author=yoh]]
 [[!tag projects/openneuro]]
+[[!meta title="warn when two special remotes with the same name are both configured to autoenable, and avoid one overwriting the git config of the other"]]

diff --git a/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_3_fe26531dcfa26b30225dc34a841153d1._comment b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_3_fe26531dcfa26b30225dc34a841153d1._comment
new file mode 100644 (file)
index 0000000..46dbb73
--- /dev/null
+++ b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_3_fe26531dcfa26b30225dc34a841153d1._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2025-08-14T14:03:08Z"
+ content="""
+Beyond a warning, it would be possible two autoenable both, but use a new
+name for the second one.
+
+It occurs to me that it's also possible for autoenable of a special remote
+to overwrite/change the git config of a regular git remote that has the
+same name. This would be unlikely except in the case of one named "origin",
+but it could happen, just needs the git remote to have been added before
+git-annex inits. That seems like a problem that ought to be avoided too.
+"""]]