From 15855fef01046e4cc568f9696d0db5c6bc5de10a Mon Sep 17 00:00:00 2001 From: anarcat Date: Tue, 25 Aug 2015 16:03:35 +0000 Subject: link to manpages so there's context over there as well --- doc/trust.mdwn | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'doc/trust.mdwn') diff --git a/doc/trust.mdwn b/doc/trust.mdwn index a33c6dd42..bfb36b5b9 100644 --- a/doc/trust.mdwn +++ b/doc/trust.mdwn @@ -20,7 +20,7 @@ There is still some trust involved here. A semitrusted repository is 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 +(Being semitrusted is the default. The [[git-annex-semitrust]] command restores a repository to this default, when it has been overridden. The `--semitrust` option can temporarily restore a repository to this default.) @@ -34,7 +34,7 @@ This is a good choice for eg, portable drives that could get lost. Or, if a disk is known to be dying, you can set it to untrusted and let `git annex fsck` warn about data that needs to be copied off it. -To configure a repository as untrusted, use the `git annex untrust` +To configure a repository as untrusted, use the [[git-annex-untrust]] command. ## trusted @@ -49,7 +49,7 @@ access a remote you trust. Or to use `--trust` to specify a repository to trust temporarily. To configure a repository as fully and permanently trusted, -use the `git annex trust` command. +use the [[git-annex-trust]] command. ## dead @@ -57,3 +57,6 @@ This is used to indicate that you have no trust that the repository exists at all. It's appropriate to use when a drive has been lost, or a directory irretrievably deleted. It will make git-annex avoid even showing the repository as a place where data might still reside. + +To configure a repository as dead and lost, use the [[git-annex-dead]] +command. -- cgit v1.2.3