From adc95a871d552de4a86cb4a1cd3c3ec2577175f3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 6 Dec 2023 15:42:40 -0400 Subject: [PATCH] comment --- ..._2_fdaef5d870221d44c57fc3bd1501e7ee._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/distributed_migration/comment_2_fdaef5d870221d44c57fc3bd1501e7ee._comment diff --git a/doc/todo/distributed_migration/comment_2_fdaef5d870221d44c57fc3bd1501e7ee._comment b/doc/todo/distributed_migration/comment_2_fdaef5d870221d44c57fc3bd1501e7ee._comment new file mode 100644 index 0000000000..40276efe9d --- /dev/null +++ b/doc/todo/distributed_migration/comment_2_fdaef5d870221d44c57fc3bd1501e7ee._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2023-12-06T19:31:42Z" + content=""" +On the `distributedmigration` branch I have `git-annex migrate` recording +migrations on the git-annex branch. + +Its method of grafting in 2 trees, one with the old keys and one with the +new is quite efficient. In a migration of 1000 files from SHA256E to SHA1, +the git objects only needs 52kb to record the migration trees. +Compared with 424 kb needed to update the location logs. +The total git repo grew from 508kb to 984k. + +Next up: Make `git-annex migrate --update` find new migrations started +elsewhere and apply them to the local annex objects. +"""]]