From 153b1e3a2bfa5bf784bf269188902ed02533864d Mon Sep 17 00:00:00 2001 From: Horus Date: Sun, 3 Mar 2019 13:21:02 +0000 Subject: [PATCH] --- .../Special_remotes_description_misleading.mdwn | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/Special_remotes_description_misleading.mdwn diff --git a/doc/forum/Special_remotes_description_misleading.mdwn b/doc/forum/Special_remotes_description_misleading.mdwn new file mode 100644 index 0000000000..1bd0db0595 --- /dev/null +++ b/doc/forum/Special_remotes_description_misleading.mdwn @@ -0,0 +1,17 @@ +Hello, + +IMHO the description of the special remotes at https://git-annex.branchable.com/special_remotes/ is misleading: + +> But, git-annex also extends git's concept of remotes, with these special types of remotes. These can be used just like any normal remote by git-annex. They cannot be used by other git commands though. + +AFAIK (and just tested it with a webdav remote), a special remote can not be used to transfer tracking information, only content. So that, in order to connect to repos that can not talk to each other, a special remote is not sufficient. You additionally need a ordinary git repo to transfer the tracking information. + +* Is that correct? Is there a way to use a special remote to transfer tracking information? (would love that!) + +The description above sounds for me, as I can simply use a special remote like a normal remote, which is not the case. + +Just a documentation improvement suggestions. + +Best Thanks, +Florian +