comment, retitle

doc/bugs/git_error___34__update__95__ref_failed_for_ref__34__.mdwn

@@ -35,3 +35,4 @@ It will download the content and fail afterwards
 ### 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)
 I am not an experienced user but after using non-space-remotes-names I've been able to sync my phone with no major problems following the documentation in this page. So great work!
 
+[[!meta title="importtree remote with spaces in its name causes ref update failure with unncessarily ugly message; could fail earlier with a better message"]]

doc/bugs/git_error___34__update__95__ref_failed_for_ref__34__/comment_1_60ea64baccef82dc03ab300ca9b5e2b5._comment

@@ -0,0 +1,26 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-05-02T18:29:05Z"
+ content="""
+This is similar to configuring git with a remote that has spaces in its
+name:
+
+	joey@darkstar:/tmp/z>git remote add "My Remote" ../x
+	fatal: 'My Remote' is not a valid remote name
+
+Or configuring a remote.foo.fetch with spaces in the name of the rev:
+
+	joey@darkstar:/tmp/y>git config remote.origin.fetch
+	+refs/heads/*:refs/remotes/Redmi Note 8/*
+	joey@darkstar:/tmp/y>git fetch origin
+	fatal: invalid refspec '+refs/heads/*:refs/remotes/Redmi Note 8/*'
+
+Importing from a special remote with importtree=yes is equivilant from
+pulling from a git remote, and needs to update a branch with a similar
+name as origin/master. And with a remote name with spaces, there is
+no legal branch name that will work.
+
+So, this has to fail. It could fail earlier, or with a better error
+message.
+"""]]