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

improve docs and close bug

Browse source
This commit is contained in:
Joey Hess 2020-08-10 12:37:25 -04:00
parent fa0aba8be6
commit 2cbebab554
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 29 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/export-tree_exports___34__small__34___files_even_if_they_don__39__t_match_the_wanted_expression.mdwn
View file

@ -18,3 +18,4 @@ Export-tree to it -> all small files in tree end up on the remote
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
I'm very impressed with git-annex overall :P
> [[wontfix|done]] --[[Joey]]

23
doc/bugs/export-tree_exports___34__small__34___files_even_if_they_don__39__t_match_the_wanted_expression/comment_1_08419003d89dab1f8b1dbfa7941b097d._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-08-10T16:22:15Z"
content="""
Preferred content expressions can have a number of terms that require a
git-annex key to evaluate. Files not managed by git-annex do not have such
keys, so it's not possible to evaluate preferred content expressions
against them.
Another way to look at it is that the export remote is equivilant to a git
remote. Pushing a git tree to a git remote necessarily stores all the files
managed by git onto that remote and so it makes sense for exporting to do
the same. (importing also always gets new versions of these small files w/o
checking the preferred content setting, equivilant to git pull.)
So, even if it were possible to match some preferred content expressions
against non-annexed files (eg ones that use only the filename or size),
I don't think it would be good for that to be done for exports.
I have improved the documentation of git-annex export to mention that
it exports all git files.
"""]]

6
doc/git-annex-export.mdwn
View file

@ -24,7 +24,11 @@ other treeish accepted by git, including eg master:subdir to only export a
subdirectory from a branch.
When the remote has a preferred content setting, the treeish is filtered
through it, excluding files it does not want from being exported to it.
through it, excluding annexed files it does not want from being exported
to it.
Any files in the treeish that are stored on git will also be exported to
the special remote.
Repeated exports are done efficiently, by diffing the old and new tree,
and transferring only the changed files, and renaming files as necessary.