mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
yarikoptic 2022-01-25 18:37:56 +00:00 committed by admin
parent d750fcdb02
commit c3817495fc
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_5_3293f29b78d10aaf9254ddba1af6731d._comment Normal file
View file

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