This file is indexed.

/usr/share/doc/git-annex/html/trust.html is in git-annex 5.20140412ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>trust</title>

<link rel="stylesheet" href="style.css" type="text/css" />

<link rel="stylesheet" href="local.css" type="text/css" />










</head>
<body>

<div class="page">

<div class="pageheader">
<div class="header">
<span>
<span class="parentlinks">

<a href="./index.html">git-annex</a>/ 

</span>
<span class="title">
trust

</span>
</span>



</div>









</div>



<div class="sidebar">
<p><img src="./logo_small.png" width="150" height="142" class="img" /></p>

<ul>
<li><a href="./install.html">install</a></li>
<li><a href="./assistant.html">assistant</a></li>
<li><a href="./walkthrough.html">walkthrough</a></li>
<li><a href="./tips.html">tips</a></li>
<li><span class="createlink">bugs</span></li>
<li><span class="createlink">todo</span></li>
<li><span class="createlink">forum</span></li>
<li><a href="./comments.html">comments</a></li>
<li><a href="./contact.html">contact</a></li>
<li><a href="http://flattr.com/thing/84843/git-annex">Flattr this</a></li>
</ul>


</div>



<div id="pagebody">

<div id="content">
<p>Git-annex supports several levels of trust of a repository:</p>

<ul>
<li>semitrusted (default)</li>
<li>untrusted</li>
<li>trusted</li>
<li>dead</li>
</ul>


<h2>semitrusted</h2>

<p>Normally, git-annex does not fully trust its stored <a href="./location_tracking.html">location tracking</a>
information. When removing content, it will directly check
that other repositories have enough <a href="./copies.html">copies</a>.</p>

<p>Generally that explicit checking is a good idea. Consider that the current
<a href="./location_tracking.html">location tracking</a> information for a remote may not yet have propagated
out. Or, a remote may have suffered a catastrophic loss of data, or itself
been lost.</p>

<p>There is still some trust involved here. A semitrusted repository is
depended on to retain a copy of the file content; possibly the only
<a href="./copies.html">copy</a>.</p>

<p>(Being semitrusted is the default. The <code>git annex semitrust</code> command
restores a repository to this default, when it has been overridden.
The <code>--semitrust</code> option can temporarily restore a repository to this
default.)</p>

<h2>untrusted</h2>

<p>An untrusted repository is not trusted to retain data at all. Git-annex
will retain sufficient <a href="./copies.html">copies</a> of data elsewhere.</p>

<p>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
<code>git annex fsck</code> warn about data that needs to be copied off it.</p>

<p>To configure a repository as untrusted, use the <code>git annex untrust</code>
command.</p>

<h2>trusted</h2>

<p>Sometimes, you may have reasons to fully trust the location tracking
information for a repository. For example, it may be an offline
archival drive, from which you rarely or never remove content. Deciding
when it makes sense to trust the tracking info is up to you.</p>

<p>One way to handle this is just to use <code>--force</code> when a command cannot
access a remote you trust. Or to use <code>--trust</code> to specify a repisitory to
trust temporarily.</p>

<p>To configure a repository as fully and permanently trusted,
use the <code>git annex trust</code> command.</p>

<h2>dead</h2>

<p>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 irretrevably deleted. It will make git-annex avoid
even showing the repository as a place where data might still reside.</p>

</div>





<div id="comments">




<div class="addcomment">Comments on this page are closed.</div>

</div>



</div>

<div id="footer" class="pagefooter">

<div id="pageinfo">






<div id="backlinks">
Links:

<a href="./copies.html">copies</a>

<a href="./internals.html">internals</a>

<a href="./location_tracking.html">location tracking</a>

<a href="./tips/offline_archive_drives.html">tips/offline archive drives</a>

<a href="./tips/untrusted_repositories.html">tips/untrusted repositories</a>

<a href="./tips/using_the_web_as_a_special_remote.html">tips/using the web as a special remote</a>

<a href="./walkthrough/removing_files:_When_things_go_wrong.html">walkthrough/removing files: When things go wrong</a>


</div>






<div class="pagedate">
Last edited <span class="date">Thu Oct 17 22:58:50 2013</span>
<!-- Created <span class="date">Thu Oct 17 22:58:50 2013</span> -->
</div>

</div>


<!-- from git-annex -->
</div>

</div>

</body>
</html>