From 14e6d7cf2dc515be5f49e35b763b63edbd4318e1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 4 Dec 2018 16:55:36 -0400 Subject: [PATCH] comment --- ...omment_1_62ef170f11f0b700a99c2749018fa234._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/clarify_that_v7_applies_to_all_clones/comment_1_62ef170f11f0b700a99c2749018fa234._comment diff --git a/doc/todo/clarify_that_v7_applies_to_all_clones/comment_1_62ef170f11f0b700a99c2749018fa234._comment b/doc/todo/clarify_that_v7_applies_to_all_clones/comment_1_62ef170f11f0b700a99c2749018fa234._comment new file mode 100644 index 0000000000..68b62235ae --- /dev/null +++ b/doc/todo/clarify_that_v7_applies_to_all_clones/comment_1_62ef170f11f0b700a99c2749018fa234._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-12-04T20:53:49Z" + content=""" +You only need to upgrade to v7 when the repository has unlocked files +committed to it. If a file contains a pointer to an annex object, it won't +work with v5. There is not a good way for git-annex to detect when that is +the case; such a file could be committed any time. Committing unlocked +files and upgrading has to be coordinated amoung the users of the repository. +"""]]