b6d46c212e
* unannex, uninit: Avoid committing after every file is unannexed,
for massive speedup.
* --notify-finish switch will cause desktop notifications after each
file upload/download/drop completes
(using the dbus Desktop Notifications Specification)
* --notify-start switch will show desktop notifications when each
file upload/download starts.
* webapp: Automatically install Nautilus integration scripts
to get and drop files.
* tahoe: Pass -d parameter before subcommand; putting it after
the subcommand no longer works with tahoe-lafs version 1.10.
(Thanks, Alberto Berti)
* forget --drop-dead: Avoid removing the dead remote from the trust.log,
so that if git remotes for it still exist anywhere, git annex info
will still know it's dead and not show it.
* git-annex-shell: Make configlist automatically initialize
a remote git repository, as long as a git-annex branch has
been pushed to it, to simplify setup of remote git repositories,
including via gitolite.
* add --include-dotfiles: New option, perhaps useful for backups.
* Version 5.20140227 broke creation of glacier repositories,
not including the datacenter and vault in their configuration.
This bug is fixed, but glacier repositories set up with the broken
version of git-annex need to have the datacenter and vault set
in order to be usable. This can be done using git annex enableremote
to add the missing settings. For details, see
http://git-annex.branchable.com/bugs/problems_with_glacier/
* Added required content configuration.
* assistant: Improve ssh authorized keys line generated in local pairing
or for a remote ssh server to set environment variables in an
alternative way that works with the non-POSIX fish shell, as well
as POSIX shells.
# imported from the archive
59 lines
2.1 KiB
Markdown
59 lines
2.1 KiB
Markdown
Git-annex supports several levels of trust of a repository:
|
|
|
|
* semitrusted (default)
|
|
* untrusted
|
|
* trusted
|
|
* dead
|
|
|
|
## semitrusted
|
|
|
|
Normally, git-annex does not fully trust its stored [[location_tracking]]
|
|
information. When removing content, it will directly check
|
|
that other repositories have enough [[copies]].
|
|
|
|
Generally that explicit checking is a good idea. Consider that the current
|
|
[[location_tracking]] 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.
|
|
|
|
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
|
|
restores a repository to this default, when it has been overridden.
|
|
The `--semitrust` option can temporarily restore a repository to this
|
|
default.)
|
|
|
|
## untrusted
|
|
|
|
An untrusted repository is not trusted to retain data at all. Git-annex
|
|
will retain sufficient [[copies]] of data elsewhere.
|
|
|
|
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`
|
|
command.
|
|
|
|
## trusted
|
|
|
|
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.
|
|
|
|
One way to handle this is just to use `--force` when a command cannot
|
|
access a remote you trust. Or to use `--trust` to specify a repisitory to
|
|
trust temporarily.
|
|
|
|
To configure a repository as fully and permanently trusted,
|
|
use the `git annex trust` command.
|
|
|
|
## dead
|
|
|
|
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.
|