diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-06-06 13:49:13 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-06-06 13:49:13 -0400 |
commit | e57492d980d410eec4956b3df8c495c03a356666 (patch) | |
tree | f6e5d6d665436e846a480b4d35f6a522c134297d | |
parent | 841207d050131b0a114a872b9cf9c84d135b1d2f (diff) |
comment
-rw-r--r-- | doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment | 17 |
1 files changed, 17 insertions, 0 deletions
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 000000000..007a1161c --- /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. +"""]] |