Merge branch 'master' of ssh://git-annex.branchable.com

doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment

@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="andrew"
+ avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
+ subject="gcrypt, git-annex and rsync requires absolute path"
+ date="2017-12-05T13:49:42Z"
+ content="""
+I struggled to get git-annex sync working for some time with gcrypt and the rsync transport protocol. It turns out I was using a relative path to my repo instead of an absolute path. In my .git/config with a url like this: `gcrypt::rsync://username@servername:relative-path-to-git-repo` where relative path is relative to my user's home directory, git push would work fine, but git-annex sync would complain it couldn't find the repository. Changing my url to an absolute path like `gcrypt::rsync://username@servername:absolute-path-to-git-repo` now allows both git-annex sync and git push to work. Andrew.
+"""]]

doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn

@@ -0,0 +1,5 @@
+Hello,
+
+sometimes, ```git annex info``` shows a (special remote) repository's name in [Brackets], sometimes not. Every theory (depending on enabled / not enabled) I had so far, is disproved by my next step. What does it means when the name is in brackets?
+
+Thanks!

doc/git-annex-export.mdwn

@@ -107,6 +107,10 @@ export`, it will detect the export conflict, and resolve it.
 
 [[git-annex-sync]](1)
 
+# HISTORY
+
+The `export` command was introduced in git-annex version 6.20170925.
+
 # AUTHOR
 
 Joey Hess <id@joeyh.name>