From c3817495fce87f83af8fb20c5725325d937eb8e1 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 25 Jan 2022 18:37:56 +0000 Subject: [PATCH] Added a comment --- ...ment_5_3293f29b78d10aaf9254ddba1af6731d._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_5_3293f29b78d10aaf9254ddba1af6731d._comment diff --git a/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_5_3293f29b78d10aaf9254ddba1af6731d._comment b/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_5_3293f29b78d10aaf9254ddba1af6731d._comment new file mode 100644 index 0000000000..c4dbf5b443 --- /dev/null +++ b/doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_5_3293f29b78d10aaf9254ddba1af6731d._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 5" + date="2022-01-25T18:37:56Z" + content=""" +cool, so I think there is one missing (from documentation) notion of the \"default\" version (in addition to \"supported\", \"upgradeable\" and \"latest\" which is = max(\"supported\")). If so -- I think +- the \"default\" version should be listed in `git annex version` as \"default version:\" in addition to \"supported\" and \"upgradable\" +- `git-annex-init` man page could say \"When the version given is older than default version, it will automatically use the newer default version instead.\" +- may be `git-annex-upgrade` man page would say \"Upgrades the repository to a supported version.\", and allow for upgrade to `default` or `latest` (probably get `--version` option to specify which?) with \"default\" being the default version to upgrade to (thus staying consistent with git-annex-init upgrading to default, not latest)? + +I think that might make present difference between \"default\" and \"latest\" clearer. +"""]]