added suggestion to use git-replace for better implement git-annex-migrate
This commit is contained in:
parent
2deb3e9129
commit
4c79f2b4ac
1 changed files with 3 additions and 0 deletions
3
doc/todo/git-annex-migrate_using_git-replace.mdwn
Normal file
3
doc/todo/git-annex-migrate_using_git-replace.mdwn
Normal file
|
@ -0,0 +1,3 @@
|
|||
Currently, git-annex-migrate leads to content (and metadata) being stored under both old and new keys. git-annex-unused can drop the contents under the old key, but then you can't access the content if you check out an older commit. Maybe, an option can be added to migrate keys using [git-replace](https://git-scm.com/docs/git-replace) ? You'd git-replace the blob .git/annex/objects/old_key with the blob .git/annex/objects/new_key, the blob ../.git/annex/objects/old_key with the blob ../.git/annex/objects/new_key , etc. You could then also have a setting to auto-migrate non-checksum keys to checksum keys whenever the contents gets downloaded.
|
||||
|
||||
More generally, git-annex-replace could be implemented this way, doing what git-replace does, but for git-annex keys rather than git hashes. [[git-annex-pre-commit]] might need to be changed to implement replacement of keys added later.
|
Loading…
Reference in a new issue