f9adb905fc
Implemented with no additional overhead of compares etc. This is safe to do for presence logs because of their locality of change; a given repo's presence logs are only ever changed in that repo, or in a repo that has just been actively changing the content of that repo. So, we don't need to worry about a split-brain situation where there'd be disagreement about the location of a key in a repo. And so, it's ok to not update the timestamp when that's the only change that would be made due to logging presence info. |
||
|---|---|---|
| .. | ||
| patches | ||
| tests | ||
| cabal-wrapper | ||
| changelog | ||
| compat | ||
| control | ||
| copyright | ||
| create-standalone-changelog | ||
| doc-base | ||
| git-annex.lintian-overrides | ||
| menu | ||
| NEWS | ||
| rules | ||