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 2017-06-06 13:49:13 -04:00
parent e0d90448b1
commit fa50906a80
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent/comment_1_ce82ccf68108d47977e32ba005098415._comment Normal file
View file

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