Avoid unncessary write to the location log when a file is unlocked and then added back with unchanged content.

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.
This commit is contained in:
Joey Hess 2015-10-12 14:46:28 -04:00
parent 82ba8c9a6a
commit f9adb905fc
Failed to extract signature
7 changed files with 65 additions and 14 deletions

4
debian/changelog vendored
View file

@ -30,11 +30,13 @@ git-annex (5.20150931) UNRELEASED; urgency=medium
* copy --auto was checking the wrong repo's preferred content.
(--from was checking what --to should, and vice-versa.)
Fixed this bug, which was introduced in version 5.20150727.
* Avoid unncessary write to the location log when a file is unlocked
and then added back with unchanged content.
* Debian: Add torrent library to build-depends as it's packaged now,
and stop recommending bittornado | bittorrent.
* Debian: Remove dependency on transformers library, as it is now
included in ghc.
-- Joey Hess <id@joeyh.name> Thu, 01 Oct 2015 12:42:56 -0400
git-annex (5.20150930) unstable; urgency=medium