File: comment_1_a921dab2c4335f690df4d5189fe4e4c2._comment

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (8 lines) | stat: -rw-r--r-- 848 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
[[!comment format=mdwn
 username="Ilya_Shlyakhter"
 avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
 subject="storing checksums for non-checksum keys in metadata"
 date="2019-08-16T16:06:29Z"
 content="""
One related improvement would be for git-annex to compute and store, as metadata, checksum-based [[keys|backends]] corresponding to non-checksum-based keys, when git-annex sees the contents of the non-checksum-based key ( e.g. [[todo/alternate_keys_for_same_content]] ). There is of course [[`git-annex-migrate`|git-annex-migrate]], but it requires manual invocation, clouds the commit history of the main git branch with commits that don't really change the content, and leads to either duplicate content in remotes or (if duplicates are dropped) inability to git-annex-get the contents of some past commits.
"""]]