From 2198ba76f7578143ed19bb7e58ffe7322e66dc96 Mon Sep 17 00:00:00 2001 From: Chel Date: Sat, 1 Feb 2020 02:55:07 +0000 Subject: [PATCH] Added a comment --- ...t_1_6a317be851dfb72c4aaaf5786dd1a1ff._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/git-annex-migrate_using_git-replace/comment_1_6a317be851dfb72c4aaaf5786dd1a1ff._comment diff --git a/doc/todo/git-annex-migrate_using_git-replace/comment_1_6a317be851dfb72c4aaaf5786dd1a1ff._comment b/doc/todo/git-annex-migrate_using_git-replace/comment_1_6a317be851dfb72c4aaaf5786dd1a1ff._comment new file mode 100644 index 0000000000..2240298a3a --- /dev/null +++ b/doc/todo/git-annex-migrate_using_git-replace/comment_1_6a317be851dfb72c4aaaf5786dd1a1ff._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="Chel" + avatar="http://cdn.libravatar.org/avatar/a42feb5169f70b3edf7f7611f7e3640c" + subject="comment 1" + date="2020-02-01T02:55:03Z" + content=""" +Very interesting idea! But some problems: + +- As mentioned, not only `.git/annex/<...>` blobs need to be replaces for every key, but also `/annex/<...>` +and all `../.git/annex/<...>`, `../../.git/annex/<...>`, etc. + +- In big repositories it can create a giant amount of *refs/replace/* refs. +I don't know how it affects the performance if they are stored in .git/packed-refs, +but it can interfere with the normal operation on a repo. +For example `git show-ref` will not work without ` | grep` or something. +"""]]