have clean filter check if the filename was already in use by an old key

The annex object for it may have been modified due to hard link, and
that should be cleaned up when the new version is added. If another
associated file has the old key's content, that's linked into the annex
object. Otherwise, update location log to reflect that content has been
lost.
This commit is contained in:
Joey Hess 2015-12-15 13:06:52 -04:00
parent 0a7a2dae4e
commit 71e2050f8f
Failed to extract signature
2 changed files with 25 additions and 4 deletions

View file

@ -325,9 +325,6 @@ files to be unlocked, while the indirect upgrades don't touch the files.
because the timestamp has changed. Getting a smudged file can also
cause this. Avoid this by preserving timestamp of smudged files
when manipulating.
* Clean filter should check if the filename was already in use by an old
key. The annex object for it may have been modified due to hard link, and
that should be cleaned up when the new version is added.
* Reconcile staged changes into the associated files database, whenever
the database is queried.
* See if the cases where the Keys database is not used can be