5fe49b98f8
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. |
||
---|---|---|
.. | ||
Backend.hs | ||
BranchState.hs | ||
Command.hs | ||
Crypto.hs | ||
FileMatcher.hs | ||
GitConfig.hs | ||
Group.hs | ||
Key.hs | ||
KeySource.hs | ||
Messages.hs | ||
Option.hs | ||
Remote.hs | ||
StandardGroups.hs | ||
TrustLevel.hs | ||
UUID.hs |