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. |
||
|---|---|---|
| .. | ||
| Committer.hs | ||
| ConfigMonitor.hs | ||
| DaemonStatus.hs | ||
| Glacier.hs | ||
| Merger.hs | ||
| MountWatcher.hs | ||
| NetWatcher.hs | ||
| PairListener.hs | ||
| Pusher.hs | ||
| SanityChecker.hs | ||
| TransferPoller.hs | ||
| Transferrer.hs | ||
| TransferScanner.hs | ||
| TransferWatcher.hs | ||
| Watcher.hs | ||
| WebApp.hs | ||
| XMPPClient.hs | ||
| XMPPPusher.hs | ||