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
30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
git-annex keeps track of in which repositories it last saw a file's content.
|
|
This location tracking information is stored in the git-annex branch.
|
|
Repositories record their UUID and the date when they get or drop
|
|
a file's content.
|
|
|
|
This location tracking information is useful if you have multiple
|
|
repositories, and not all are always accessible. For example, perhaps one
|
|
is on a home file server, and you are away from home. Then git-annex can
|
|
tell you what git remote it needs access to in order to get a file:
|
|
|
|
# git annex get myfile
|
|
get myfile (not available)
|
|
I was unable to access these remotes: home
|
|
|
|
Another way the location tracking comes in handy is if you put repositories
|
|
on removable USB drives, that might be archived away offline in a safe
|
|
place. In this sort of case, you probably don't have a git remotes
|
|
configured for every USB drive. So git-annex may have to resort to talking
|
|
about repository UUIDs. If you have previously used "git annex init"
|
|
to attach descriptions to those repositories, it will include their
|
|
descriptions to help you with finding them:
|
|
|
|
# git annex get myfile
|
|
get myfile (not available)
|
|
Try making some of these repositories available:
|
|
c0a28e06-d7ef-11df-885c-775af44f8882 -- USB archive drive 1
|
|
e1938fee-d95b-11df-96cc-002170d25c55
|
|
|
|
In certain cases you may want to configure git-annex to [[trust]]
|
|
that location tracking information is always correct for a repository.
|