From 4d593d4461721478562bdd63a02955d2bcdb0ae3 Mon Sep 17 00:00:00 2001 From: ErrGe Date: Fri, 11 Mar 2022 02:23:20 +0000 Subject: [PATCH] Added a comment --- ...mment_2_6e735205024588497a116ce9e7e621a9._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/force_star_topology_on_a_repository/comment_2_6e735205024588497a116ce9e7e621a9._comment diff --git a/doc/todo/force_star_topology_on_a_repository/comment_2_6e735205024588497a116ce9e7e621a9._comment b/doc/todo/force_star_topology_on_a_repository/comment_2_6e735205024588497a116ce9e7e621a9._comment new file mode 100644 index 0000000000..e7038489dc --- /dev/null +++ b/doc/todo/force_star_topology_on_a_repository/comment_2_6e735205024588497a116ce9e7e621a9._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="ErrGe" + avatar="http://cdn.libravatar.org/avatar/37423d3bfd69af2cda23d194ec74f991" + subject="comment 2" + date="2022-03-11T02:23:20Z" + content=""" +Thank you for reading and replying to my feature request. + +I agree with most of what you have said, and I agree that making `annex.private` `git-annex config`urable is 99% of my feature request. + +I wrote the rest of the text, because I actually had a case, while testing this star topology thing where an uuid crept into the git-annex branch and it was coming from testing a special remote with rclone and not being careful enough with it. So, I think the global `annex.private` variable somehow also has to support special remotes and then there has to be a way to opt-out the one special remote, that is the real center of the star topology. +"""]]