add v6; keep v5 working for now and manual upgrade
Since all places where a repo is used in direct mode need to have git-annex upgraded before the repo can safely be converted to v6, the upgrade needs to be manual for now. I suppose that at some point I'll want to drop all the direct mode support code. At that point, will stop supporting v5, and will need to auto-upgrade any remaining v5 repos. If possible, I'd like to carry the direct mode support for say, a year or so, to give people plenty of time to upgrade and avoid disruption.
This commit is contained in:
parent
34ead644d9
commit
ccc49861ca
9 changed files with 74 additions and 14 deletions
|
@ -308,15 +308,17 @@ annex.version changes to 6
|
|||
|
||||
Upgrade should be handled automatically.
|
||||
|
||||
On upgrade, update .gitattributes with a stock configuration, unless
|
||||
it already mentions "filter=annex".
|
||||
On upgrade, update $GIT_DIR/info/attributes with a stock configuration,
|
||||
unless it already mentions "filter=annex".
|
||||
|
||||
Upgrading a direct mode repo needs to switch it out of bare mode, and
|
||||
needs to run `git annex unlock` on all files (or reach the same result).
|
||||
So will need to stage changes to all annexed files.
|
||||
|
||||
When a repo has some clones indirect and some direct, the upgraded repo
|
||||
will have all files unlocked, necessarily in all clones.
|
||||
will have all files unlocked, necessarily in all clones. This happens
|
||||
automatically, because when the direct repos are upgraded that causes the
|
||||
files to be unlocked, while the indirect upgrades don't touch the files.
|
||||
|
||||
----
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue