Joey Hess e05dd70544 handle upgrading repositories initialized with --version=9 ... As was attempted earlier in the buggy commit 0d2e3058ee Avoided the bug that had by making the upgrade log be updated after each upgrade step. So, after upgrade from v8 to v9, the log is updated, and so Upgrade.V9's timeOfUpgrade check will find that it was upgraded recently and so won't let it skip ahead to v10. Sponsored-by: k0ld on Patreon		2022-09-26 12:59:51 -04:00
..
V5	avoid creating content directory when locking content	2022-05-16 12:34:56 -04:00
V0.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V1.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V2.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V3.hs	update licenses from GPL to AGPL	2019-03-13 15:48:14 -04:00
V4.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V5.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V6.hs	split upgrade into v9 and v10	2022-01-19 13:09:33 -04:00
V7.hs	add annex.dbdir (WIP)	2022-08-11 16:58:53 -04:00
V8.hs	enable filter.annex.process in v9	2022-01-21 13:11:18 -04:00
V9.hs	handle upgrading repositories initialized with --version=9	2022-09-26 12:59:51 -04:00