e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # 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.
|