jump right to v8, don't stop part way
* init --version: When the version given is one that automatically upgrades to a newer version, use the newer version instead. * Auto upgrades from older repo versions, like v5, now jump right to v8.
This commit is contained in:
parent
08d0b44f4d
commit
1bb32098d6
5 changed files with 36 additions and 5 deletions
|
@ -49,3 +49,5 @@ lucky and it's passable Haskell, I'd be happy to send a patch.
|
|||
|
||||
[[!meta author=kyle]]
|
||||
[[!tag projects/datalad]]
|
||||
|
||||
> [[fixed|done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,23 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2020-02-24T17:13:45Z"
|
||||
content="""
|
||||
Your patch is perfectly fine haskell code.
|
||||
|
||||
But, looking at it, the problem is deeper than init --version.
|
||||
Running git-annex in a v3 repo produces a v5 repo,
|
||||
then running git-annex again produces a v6 repo,
|
||||
then v7, then v8.
|
||||
|
||||
So the problem is really that autoUpgradeableVersions
|
||||
should map everything to latestVersion. At least currently,
|
||||
since all versions should be upgraded to v8.
|
||||
|
||||
(Really it could just be a list of versions that all
|
||||
are assumed to upgrade to latestVersion, but I left it a map
|
||||
in case at some point there are two concurrent version
|
||||
tracks without an autoupgrade between them.)
|
||||
|
||||
Anyway, attach a git format-patch next time so I can git am it. :)
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue