Added a comment

1 files changed, 10 insertions, 0 deletions

diff --git a/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 b/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
new file mode 100644
index 000000000..386ea5e2d
--- /dev/null
+++ b/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
@@ -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.
+"""]]