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 2022-01-24 15:16:14 -04:00
parent 0ee9ccb00f
commit 29e8636a88
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/init__58___autoupgrade___60__8_annex_version_to_8_not_10/comment_1_5b9ba56f682a991a57872d021f2ff08e._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-01-24T19:11:03Z"
content="""
Hmm, the git-annex-upgrade man page says "Upgrades the repository to the latest version"
and v10 is the latest version now. --version=8 will do what you want.
I think that people would generally be surprised if `git-annex upgrade` did
not upgrade to the latest supported version.
As for `git-annex init --version=6`, v6 is not a supported version, so that
was upgrading to v8 before. The git-annex-init man page says
"When the version given is one that automatically upgrades to a newer
version, it will automatically use the newer version instead."
and v6 does automatically upgrade to v10 now, so again this behavior is
following the documentation. Although so I suppose would be using v8 in the
brief amount of time v10 is not upgraded to by default.
"""]]