diff --git a/CHANGELOG b/CHANGELOG
index 41b29b94fc..6db433a60e 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -57,6 +57,7 @@ git-annex (7.20200226) upstream; urgency=high
     on those remotes without encrypting it.
     If your remotes are affected, you will want to make sure to delete
     any content that git-annex has stored on them that is not encrypted!
+  * initremote: Fix regression in parsing the exporttree= parameter.
   * info: Fix display of the encryption value.
     (Some debugging junk had crept in.)
   * Bugfix to getting content from an export remote with -J, when the
diff --git a/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree.mdwn b/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree.mdwn
index 26d8cc4966..6c26d4e737 100644
--- a/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree.mdwn
+++ b/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree.mdwn
@@ -49,3 +49,5 @@ local repository version: 7
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 Yes!
+
+> [[fixed|done]] --[[Joey]]
diff --git a/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree/comment_1_059d50419385a16fbddc96d85debb439._comment b/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree/comment_1_059d50419385a16fbddc96d85debb439._comment
new file mode 100644
index 0000000000..1c14639154
--- /dev/null
+++ b/doc/bugs/git-annex__58___Unexpected_parameters__58___exporttree/comment_1_059d50419385a16fbddc96d85debb439._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-03-02T17:20:36Z"
+ content="""
+This was already fixed in git-annex 7.20200226, it turns out.
+Some changes required to deal with a related reversion fixed it in passing.
+
+(Note that exporttree=no is the default, so there should
+be no need to specify it.)
+"""]]