From 9f625837177dc2fcfc5d95c51f43fd19fe9de797 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 16 Aug 2019 16:02:41 +0000 Subject: [PATCH] Added a comment: storing checksums for non-checksum keys in metadata --- .../comment_1_505eb7cf1da3e63e5e4f018391712761._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/URL_key_potential_data_loss/comment_1_505eb7cf1da3e63e5e4f018391712761._comment diff --git a/doc/bugs/URL_key_potential_data_loss/comment_1_505eb7cf1da3e63e5e4f018391712761._comment b/doc/bugs/URL_key_potential_data_loss/comment_1_505eb7cf1da3e63e5e4f018391712761._comment new file mode 100644 index 0000000000..0bb26b27f2 --- /dev/null +++ b/doc/bugs/URL_key_potential_data_loss/comment_1_505eb7cf1da3e63e5e4f018391712761._comment @@ -0,0 +1,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:02:41Z" + content=""" +One related improvement would be for git-annex to compute and store, as metadata, checksum-based keys 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]], 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. +"""]]