summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2014-12-18 15:58:28 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2014-12-18 15:58:28 -0400
commit932bead0a4f86cd2f883e49cb1b71df7d3b2ede7 (patch)
tree0eed398d959c9679834e3df02d751f5568d17940
parent95064d074fe166de5dff1c5f500627c95e63e30e (diff)
note about trust and checking copies
-rw-r--r--doc/special_remotes/bittorrent.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/special_remotes/bittorrent.mdwn b/doc/special_remotes/bittorrent.mdwn
index 4821acc63..b9bbff61a 100644
--- a/doc/special_remotes/bittorrent.mdwn
+++ b/doc/special_remotes/bittorrent.mdwn
@@ -20,3 +20,10 @@ it cannot upload or remove content.
Multi-file torrents are supported; to handle them, `git annex addurl`
will add a directory containing all the files from the torrent.
+
+It's hard to say if a torrent is healthy enough to let a file be downloaded
+from it, and harder to predict if a torrent will stay healthy. So,
+git-annex takes a cautious approach and when dropping a file, won't
+treat this special remote as one of the required [[copies]]. It's probably
+a good idea to configure git-annex to fully distrust this remote, by
+running `git annex untrust bittorrent`