From 153b1e3a2bfa5bf784bf269188902ed02533864d Mon Sep 17 00:00:00 2001 From: Horus Date: Sun, 3 Mar 2019 13:21:02 +0000 Subject: [PATCH 1/3] --- .../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 + From 81c747ba69d73f9b0924f1f451174073fe0e31d3 Mon Sep 17 00:00:00 2001 From: Horus Date: Mon, 4 Mar 2019 08:59:22 +0000 Subject: [PATCH 2/3] Added a comment --- .../comment_1_5226553dd5f529e3e4882ea18c3be600._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Special_remotes_description_misleading/comment_1_5226553dd5f529e3e4882ea18c3be600._comment diff --git a/doc/forum/Special_remotes_description_misleading/comment_1_5226553dd5f529e3e4882ea18c3be600._comment b/doc/forum/Special_remotes_description_misleading/comment_1_5226553dd5f529e3e4882ea18c3be600._comment new file mode 100644 index 0000000000..81a00008f9 --- /dev/null +++ b/doc/forum/Special_remotes_description_misleading/comment_1_5226553dd5f529e3e4882ea18c3be600._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Horus" + avatar="http://cdn.libravatar.org/avatar/8f0ee08b98ea5bba76c3fe112c08851c" + subject="comment 1" + date="2019-03-04T08:59:21Z" + content=""" +Another small thing, at I think `annex-rsync-transport` should be `annex.rsync-transport`. At least for me, it only worked that way. +"""]] From b7af89a8b40d9a5da8ee79452f9ff019c15dd63b Mon Sep 17 00:00:00 2001 From: "tjbk123@277355c7f00c6df42e960e85caafa4b294872337" Date: Tue, 5 Mar 2019 18:23:03 +0000 Subject: [PATCH 3/3] Added a comment: Best solution to save disk space on exFAT --- .../comment_8_9e5d1a9523239cb601612951af5eb9f1._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_8_9e5d1a9523239cb601612951af5eb9f1._comment diff --git a/doc/tips/unlocked_files/comment_8_9e5d1a9523239cb601612951af5eb9f1._comment b/doc/tips/unlocked_files/comment_8_9e5d1a9523239cb601612951af5eb9f1._comment new file mode 100644 index 0000000000..13235ea927 --- /dev/null +++ b/doc/tips/unlocked_files/comment_8_9e5d1a9523239cb601612951af5eb9f1._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="tjbk123@277355c7f00c6df42e960e85caafa4b294872337" + nickname="tjbk123" + avatar="http://cdn.libravatar.org/avatar/8957c069e5030708a4c144b658437b49" + subject="Best solution to save disk space on exFAT" + date="2019-03-05T18:23:03Z" + content=""" +I see that `annex.thin` doesn't support FAT. What's the best option to save disk space when you *are* using FAT? I'm currently trying to put files that are more than 50% of a drive's size on that drive, with a v7 repository. Is that possible? +"""]]