From 50d99e19a3a13b5357a50adc095805bb40286521 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 29 Oct 2018 19:43:25 +0000 Subject: [PATCH] added suggestion about supporting alternate keys for same content --- doc/todo/alternate_keys_for_same_content.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 doc/todo/alternate_keys_for_same_content.mdwn diff --git a/doc/todo/alternate_keys_for_same_content.mdwn b/doc/todo/alternate_keys_for_same_content.mdwn new file mode 100644 index 0000000000..92df3f7c90 --- /dev/null +++ b/doc/todo/alternate_keys_for_same_content.mdwn @@ -0,0 +1,6 @@ +Designate a metadata field, say alt_keys, to store alternate keys for the content designated by the key with the metadata. +Then, after initially adding a URL key, and after some time getting its content, a checksum-based key such as MD5 could be added as the URL key's metadata. +Then, without needing to migrate, the URL key could be treated like checksum-based keys, e.g. downloaded from untrusted remotes, fsck'ed, etc. + +The problem with migrating keys is that a separate copy of the contents is stored in the annex under the old key; but it you force-drop that, symlinks in +older commits will become invalid. You could rewrite git history, but that brings its own problems.