From 7ea3489ceb7dd201dc6dd01907f8c546f1bacbc1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 7 Feb 2018 15:13:11 -0400 Subject: comment --- ...omment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/design/exporting_trees_to_special_remotes/comment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment diff --git a/doc/design/exporting_trees_to_special_remotes/comment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment b/doc/design/exporting_trees_to_special_remotes/comment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment new file mode 100644 index 000000000..c67370a07 --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 19""" + date="2018-02-07T19:04:03Z" + content=""" +What if the remote wants to use some feature like NOTE, but can still +manage to work when an old git-annex does not support it? Hard bumping the +VERSION cannot support that. If the remote requires to be able to use NOTE +and sees it cannot, it can still throw an error. + +There are a bunch of requests in the protocol that are optional for the +remote to support; git-annex deals with remotes that don't support them in +better ways than throwing up its hands because the special remote is too +old. It's very good that the protocol allowed adding those extensions +without bumping a version. The protocol is less extensible when it comes +replies and other messages sent by the special remote, and I want to get +the same extensibility for those. +"""]] -- cgit v1.2.3