From 9a35831ac3e5fc7f4fe7da2e90c1b13edc2cff7b Mon Sep 17 00:00:00 2001 From: Joey Hess <joeyh@joeyh.name> Date: Wed, 7 Feb 2018 12:47:07 -0400 Subject: [PATCH] response --- ...t_18_fe77370699b7ce0acd547fd1e045e254._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/design/exporting_trees_to_special_remotes/comment_18_fe77370699b7ce0acd547fd1e045e254._comment diff --git a/doc/design/exporting_trees_to_special_remotes/comment_18_fe77370699b7ce0acd547fd1e045e254._comment b/doc/design/exporting_trees_to_special_remotes/comment_18_fe77370699b7ce0acd547fd1e045e254._comment new file mode 100644 index 0000000000..bebfee6ed5 --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_18_fe77370699b7ce0acd547fd1e045e254._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 18""" + date="2018-02-07T16:43:02Z" + content=""" +Changing VERSION would prevent any older versions of git-annex from working +with that external special remote, since they would reject the unknown +version. (The current parsing of VERSION also happens to preclude adding +some fields after the number.) + +Since it seems completely possible to make the protocol be changed in a way +that is backwards compatible both ways, while still letting new features to +be used, I'd rather reserve changing VERSION for whatever future thing +needs a full breaking bump. +"""]]