upgrading
This commit is contained in:
parent
408659b00b
commit
fe55caa2ae
1 changed files with 19 additions and 0 deletions
|
@ -185,6 +185,9 @@ Configuration:
|
|||
the annex. Other files are passed through the smudge/clean as-is and
|
||||
have their contents stored in git.
|
||||
|
||||
* annex.direct is repurposed to configure how the assistant adds files.
|
||||
When set to true, they're added unlocked.
|
||||
|
||||
git-annex clean:
|
||||
|
||||
* Run by `git add` (and diff and status, etc), and passed the
|
||||
|
@ -256,6 +259,22 @@ based on when I see smudge/clean filters being run. The file2key
|
|||
optimisation may not be needed though, looking at the index
|
||||
might be fast enough.
|
||||
|
||||
#### Upgrading
|
||||
|
||||
annex.version changes to 6
|
||||
|
||||
Upgrade should be handled automatically.
|
||||
|
||||
On upgrade, update .gitattributes 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.
|
||||
|
||||
----
|
||||
|
||||
### test files
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue