diff options
| author |  Cyberthal <Cyberthal@web> | 2017-03-24 15:10:10 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-03-24 15:10:10 +0000 |
| commit | a25ecd104df3e97b6d50030a11562aae71a56657 (patch) | |
| tree | c739898380fa1030bb8be3a794e1bfe40bc5df13 /doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn | |
| parent | ea8ff6980baafa4ae0075323af4e84cb8739c236 (diff) | |
Diffstat (limited to 'doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn')
| -rw-r--r-- | doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn b/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn new file mode 100644 index 000000000..4defa7437 --- /dev/null +++ b/doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn @@ -0,0 +1,8 @@ +by default, git-annex will set repo version to v5 +--even if I clone a v6 repo +--or sync from a v6 repo +----(if I sync and there is a git remote in the network which hasn't been git annex initialized yet, it become a v5 repo in its config file) + +so I must always upgrade after creating a new repo, or else specify v6 in the creation command. + +Given the potential negative effects of mixed version networks, it is probably best to follow the version of the repo cloned, unless the version is specified in the command. |