From 76a1e5cb6c06c80ecf2fa45b224a3dd148590d92 Mon Sep 17 00:00:00 2001
From: "jonas@ab8487518c600ac0c785f4f6ca641c219f2bcfdc" <jonas@web>
Date: Sun, 6 Feb 2022 23:29:02 +0000
Subject: [PATCH]

---
 ...ting_forgetfulness_does_not_propagate.mdwn | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 doc/forum/No_luck_getting_forgetfulness_does_not_propagate.mdwn

diff --git a/doc/forum/No_luck_getting_forgetfulness_does_not_propagate.mdwn b/doc/forum/No_luck_getting_forgetfulness_does_not_propagate.mdwn
new file mode 100644
index 0000000000..cd5b187703
--- /dev/null
+++ b/doc/forum/No_luck_getting_forgetfulness_does_not_propagate.mdwn
@@ -0,0 +1,26 @@
+I am not having any luck throwing away historical data using `git annex forget`. According to the manpage "the forgetfulness will automatically propagate out", but what I observe is that the old metadata is merged right back into the branch with the truncated metadata:
+
+```
+$ git annex forget --force --drop-dead
+$ git annex sync B3
+$ git log --branches --remotes --oneline --graph
+*   e7cf462ada (B3/synced/git-annex, B3/git-annex, git-annex) merging B3/git-annex into git-annex
+|\  
+| * 7f8b737a01 update
+* | 41bef1e3db merging B3/git-annex into git-annex
+|\| 
+| * 383a53bf9a update
+| *   2607574ed0 merging B3/git-annex into git-annex
+| |\  
+| | * dc46f334c9 update
+| * | c4c25c52a7 new branch for transition ["forget git history","forget dead remotes"]
+|  /  
+* / d3a1042f9e new branch for transition ["forget git history","forget dead remotes"]
+ /
+ |
+(here comes all of the old history)
+```
+
+What else do I have to do to make this happen?
+
+Thanks for your support! -- Jonas