From fa50906a80589a2f231aa7387ce62d46390a1349 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 6 Jun 2017 13:49:13 -0400 Subject: [PATCH] comment --- ..._1_ce82ccf68108d47977e32ba005098415._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment diff --git a/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment b/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment new file mode 100644 index 0000000000..007a1161cf --- /dev/null +++ b/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-06-06T17:45:40Z" + content=""" +I don't feel that the benefits of doing this would be worth the added +complexity. v6 repositories are still an experimental feature, and just +because one user is using them does not mean another user necessarily +will want to. One user might be using a v6 repository with `git annex +adjust --unlock`, and if so it will remain compatible with v5 clones. +Only if unlocked files are being committed to a v6 repository is there +a backwards compatability problem. + +And, when there's a central git repository, one clone might be using v6 +mode but clonding from the central repo would still produce a v5 repo, +so making this change wouldn't help at all with a common case. +"""]]