use GIT keys for export of non-annexed files
This solves the problem that import of such files gets confused and converts them back to annexed files. The import code already used GIT keys internally when it determined a file should not be annexed. So now when it sees a GIT key that export used, it already does the right thing. This also means that even older version of git-annex can import and will do the right thing, once a fixed version has exported. Still, there may be other complications around upgrades; still need to think it all through. Moved gitShaKey and keyGitSha from Key to Annex.Export since they're only used for export/import. Documented GIT keys in backends, since they do appear in the git-annex branch now. This commit was sponsored by Graham Spencer on Patreon.
This commit is contained in:
parent
deac6f12b5
commit
fc61915230
6 changed files with 80 additions and 88 deletions
|
@ -76,6 +76,10 @@ content of an annexed file remains unchanged.
|
|||
passing it to a shell script. The URL-backend key is distinct from URLs/URIs
|
||||
that may be attached to a key (from any backend) indicating the key's location
|
||||
on the web or in one of [[special_remotes]].
|
||||
* `GIT` -- This is used internally by git-annex when exporting trees
|
||||
containing files stored in git, rather than git-annex. It represents a
|
||||
git sha. This is never used for git-annex links, but information about
|
||||
keys of this type is stored in the git-annex branch.
|
||||
|
||||
## external backends
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue