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

Added a comment

Browse source
This commit is contained in:
timothyhobbs@8b50ff958c937fa4b6de1f9009f464b9ddfc2991 2016-04-05 09:19:59 +00:00 • committed by admin
parent 08897ff3a2
commit 886f5b2d12
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/bugs/Can__39__t_add_a_git_repo_to_git_annex__58_____34__Invalid_path_repo__47__.git__47__X__34___for_many_X/comment_22_5c15f550afc28c122a5050004ce913a1._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="timothyhobbs@8b50ff958c937fa4b6de1f9009f464b9ddfc2991"
nickname="timothyhobbs"
subject="comment 22"
date="2016-04-05T09:19:59Z"
content="""
You are right, that the merging picture doesn't work out if you have a \"single entity\" spread across multiple files. Whether that be a version control system like git or mercurial, or a package unpacked by a package manager. I do not plan on doing any merging. I want to esencially store the file trees of Docker images in git annex. What does it even mean to merge two Docker images? Would you expect that when merging an image based on a debian base image which has git installed, with one that has vim installed, that you would get an image with both git and vim? That would be cool, obviously, but I don't think that it is going to happen, and I don't need it to. OSTree doesn't have merging. You cannot merge two Docker images which happen to be based on the same base image...
So while it is true, that tracking multifile entities in git-annex breaks merging, that doesn't make it silly.
"""]]