mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2018-02-07 15:13:11 -04:00
parent 4abf473b52
commit 1f696ac30c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/design/exporting_trees_to_special_remotes/comment_19_1eda1af40f6ca82a8bacd19afaa749bc._comment Normal file
View file

@ -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.
"""]]