To support this, a core.gcrypt-id is stored by git-annex inside the git config of a local gcrypt repository, when setting it up. That is compared with the remote's cached gcrypt-id. When different, a drive has been changed. git-annex then looks up the remote config for the uuid mapped from the core.gcrypt-id, and tweaks the configuration appropriately. When there is no known config for the uuid, it will refuse to use the remote. |
||
|---|---|---|
| .. | ||
| Helper | ||
| Bup.hs | ||
| Directory.hs | ||
| GCrypt.hs | ||
| Git.hs | ||
| Glacier.hs | ||
| Hook.hs | ||
| List.hs | ||
| Rsync.hs | ||
| S3.hs | ||
| Web.hs | ||
| WebDAV.hs | ||