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

followup and break out todo item to prioritize

Browse source
This commit is contained in:
Joey Hess 2020-06-16 14:25:51 -04:00
parent 3922f34f8e
commit d4d0951c07
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/Mixed_content_repos_with_import_and_export/comment_1_0486a067491456d92220ca638e3095bf._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-06-16T18:17:19Z"
content="""
This is one of the still open items in [[todo/import_tree]],
namely "Need to support annex.largefiles when importing"
I don't think there's any major issue implementing it, other than it being
a bit of bother due to things like matching on mime type. I've lifted that
todo out to [[todo/import_tree_should_honor_annex.largefiles]] so hopefully
it'll be more of an action item on my todo list rather than buried away.
"""]]

1
doc/todo/import_tree.mdwn
View file

@ -51,6 +51,7 @@ and `git annex sync --content` can be configured to use it.
would thus benefit both uses cases. would thus benefit both uses cases.
* Need to support annex.largefiles when importing. * Need to support annex.largefiles when importing.
[[todo/import_tree_should_honor_annex.largefiles]]
* If a tree containing a non-annexed file is exported, * If a tree containing a non-annexed file is exported,
and then an import is done from the remote, the new tree will have that and then an import is done from the remote, the new tree will have that

13
doc/todo/import_tree_should_honor_annex.largefiles.mdwn Normal file
View file

@ -0,0 +1,13 @@
Need to support annex.largefiles when importing a tree from a special
remote.
Note that the legacy `git annex import` from a directory does honor
annex.largefiles.
The tricky bit might be that the largefiles matcher will need to run on
the temporary annex key that's used to import, before calculating the real
annex key; there's no corresponding file in the working tree. Also,
a "branch:subdir" at the command line or in
remote.name.annex-tracking-branch can change the path
that the file is being imported to, which needs to be communicated to the
largefiles matcher.