From 4414e97b9b9508b6f82e0fc763bd7c9fe3ae65b1 Mon Sep 17 00:00:00 2001 From: Spencer Date: Wed, 19 Feb 2025 23:08:42 +0000 Subject: [PATCH] Added a comment: For Those Who Stumble Here --- ...mment_3_676c0dc0053e4bbec300a083ad61d0b7._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/deleting_a_repository_from_history/comment_3_676c0dc0053e4bbec300a083ad61d0b7._comment diff --git a/doc/todo/deleting_a_repository_from_history/comment_3_676c0dc0053e4bbec300a083ad61d0b7._comment b/doc/todo/deleting_a_repository_from_history/comment_3_676c0dc0053e4bbec300a083ad61d0b7._comment new file mode 100644 index 0000000000..ff2cacc26b --- /dev/null +++ b/doc/todo/deleting_a_repository_from_history/comment_3_676c0dc0053e4bbec300a083ad61d0b7._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Spencer" + avatar="http://cdn.libravatar.org/avatar/2e0829f36a68480155e09d0883794a55" + subject="For Those Who Stumble Here" + date="2025-02-19T23:08:41Z" + content=""" +In my testing, I have found `git annex forget --drop-dead --force` problematic because if **ever** the two repositories speak to one another (thru e.g. fetch) again, the very alive remote for one marked dead in the other will be eradicated. + +Luckily I've learned that **you don't have to fetch from one remote to another to still issue \"informed\" annex commands** which is critical. In other words, I didn't appreciate how annex learns of file content in remotes dynamically, I thought it was fairly dependent on merging in the `git-annex` branch to learn about files. Instead you can confidently treat `fetch`, `pull`, `push` commands as all *exclusively* for the merging of two sibling repos (and their histories, settings, remotes, etc). + +For these kinds of (\"friend\"?) remotes (unrelated remotes), I think you'll want to remove the fetch refspec entirely and add `annex-sync=false` if you want to keep the relationship around, otherwise **never run `sync`** until you remove unrelated remotes. +"""]]