From 0bcb944870af38bb8eec9e4e0dcfb7ba7d6beff4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 26 Jan 2022 13:26:55 -0400 Subject: [PATCH] comment --- ...6_f09aa0ebe68b5db72d466ae802ce20d5._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_6_f09aa0ebe68b5db72d466ae802ce20d5._comment diff --git a/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_6_f09aa0ebe68b5db72d466ae802ce20d5._comment b/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_6_f09aa0ebe68b5db72d466ae802ce20d5._comment new file mode 100644 index 0000000000..20c1f636c8 --- /dev/null +++ b/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_6_f09aa0ebe68b5db72d466ae802ce20d5._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2022-01-26T17:05:34Z" + content=""" +I think you are making this a lot more complex than it will appear to any +user. These versions are almost indistinguishable by the user; v9 is +literally one git config change from v8. + +And also, I reserve the right to make it do *anything that makes sense* +around upgrades. Overspecifying the behavior will constrain future +upgrades. Repository upgrades often already involve threading a very fine +needle, making the hole artificially smaller does not seem wise. + +I suspect your test suite is unncessarily fragile around git-annex +repository version numbers, perhaps that is the real root of your +problem? +"""]]