aboutsummaryrefslogtreecommitdiff
path: root/doc/trust.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-06-01 17:49:37 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-06-01 17:57:31 -0400
commita8fb97d2ce8e75b36b8e1572a83efd341e67d43e (patch)
treeab24a8af581281ff8b006309acfb4000317ad072 /doc/trust.mdwn
parent7a3d9d8c2e2bd53d0d4290e99186c6e37f18456d (diff)
Add --trust, --untrust, and --semitrust options.
Diffstat (limited to 'doc/trust.mdwn')
-rw-r--r--doc/trust.mdwn11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/trust.mdwn b/doc/trust.mdwn
index 317e4b541..7505a7af6 100644
--- a/doc/trust.mdwn
+++ b/doc/trust.mdwn
@@ -20,7 +20,9 @@ depended on to retain a copy of the file content; possibly the only
[[copy|copies]].
(Being semitrusted is the default. The `git annex semitrust` command
-restores a repository to this default, when it has been overridden.)
+restores a repository to this default, when it has been overridden.
+The `--semitrust` option can temporarily restore a repository to this
+default.)
## untrusted
@@ -42,7 +44,8 @@ archival drive, from which you rarely or never remove content. Deciding
when it makes sense to trust the tracking info is up to you.
One way to handle this is just to use `--force` when a command cannot
-access a remote you trust.
+access a remote you trust. Or to use `--trust` to specify a repisitory to
+trust temporarily.
-To configure a repository as fully trusted, use the `git annex trust`
-command.
+To configure a repository as fully and permanently trusted,
+use the `git annex trust` command.