mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

document preferred content for import/export

Browse source
This commit is contained in:
Joey Hess 2020-08-10 15:35:26 -04:00
parent 9358ff8bc1
commit a354263a19
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 38 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/bugs/export-tree_exports___34__small__34___files_even_if_they_don__39__t_match_the_wanted_expression/comment_4_aa029562ec76e83ecc5e6fc76355ad96._comment Normal file
View file

@ -0,0 +1,26 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-08-10T19:18:13Z"
content="""
Understandable mistake. If you might have more such files,
you can `git config annex.dotfiles true`
> Also, I was surprised to find that include= expressions were relative to
> the part of the tree I was exporting and not the git-annex root ?
Well, if you run `git annex export somesha --to remote`, all it knows is
the tree for that sha, so it has to match relative to the top of that tree,
and not whatever other tree it might be embedded in on master or wherever.
When you run `git annex export master:subdir --to remote`, it has enough
information that it could match relative to the top of master, but that
would be inconsistent.
And the same with a config setting annex-tracking-branch to master:subdir.
Import does also do the same thing, it has to also for consistency of
course.
I have mentioned this in the docs now.
"""]]