From a25ecd104df3e97b6d50030a11562aae71a56657 Mon Sep 17 00:00:00 2001 From: Cyberthal Date: Fri, 24 Mar 2017 15:10:10 +0000 Subject: --- ...ault_annex_version_match___40__clone_or_sync__41___parent.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn (limited to 'doc/todo/Make_default_annex_version_match___40__clone_or_sync__41___parent.mdwn') 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. -- cgit v1.2.3