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

Added a comment: One possible workaround

Browse source
This commit is contained in:
EvanDeaubl 2021-02-22 16:23:41 +00:00 committed by admin
parent 4381ad636e
commit abb70e83dd
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/indeterminite_preferred_content_state_for_duplicated_file/comment_2_085f54265ce94186fe715df297785496._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="EvanDeaubl"
avatar="http://cdn.libravatar.org/avatar/00804f84646da416472678b573fd9d30"
subject="One possible workaround"
date="2021-02-22T16:23:40Z"
content="""
I ran into this exact situation trying to split content across multiple repos by directory, and ran into a couple of files with many duplicate keys throughout the repo. I worked around it by applying a tag to the offending key, and including that tag as part of the preferred content expression:
```
git annex metadata -t common-signature $FILE_WITH_DUP_KEY
git annex wanted . 'include=\"foo/*\" or include \"bar/*\" or metadata=tag=common-signature'
```
This would result in a file possibly being included in a repo where it wouldn't be otherwise (if it wasn't in one of the include directories to begin with), but in my case, the common files were few and small (2, both less than 100K).
"""]]