diff options
| author |  http://joey.kitenet.net/ <joey@web> | 2012-01-03 17:00:53 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-01-03 17:00:53 +0000 |
| commit | 79f9a2d18d5211f81d27a2ef0f57f5e14b5ef99e (patch) | |
| tree | 1e1cb3fc4be75fe58ddc9a44f0458544273f884f | |
| parent | 69875de8ea7aefdabec1ff81c567c8c5158ed5c1 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/git-subtree_support__63__/comment_1_4f333cb71ed1ff259bbfd86704806aa6._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/git-subtree_support__63__/comment_1_4f333cb71ed1ff259bbfd86704806aa6._comment b/doc/forum/git-subtree_support__63__/comment_1_4f333cb71ed1ff259bbfd86704806aa6._comment new file mode 100644 index 000000000..e4ded4c57 --- /dev/null +++ b/doc/forum/git-subtree_support__63__/comment_1_4f333cb71ed1ff259bbfd86704806aa6._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joey.kitenet.net/" + nickname="joey" + subject="comment 1" + date="2012-01-03T17:00:53Z" + content=""" +I have no experience using git-subtree, but as long as the home repository has the work one as a git remote, it will automatically merge work's git-annex branch with its own git-annex branch, and so will know what files are present at work, and will be able to get them. + +Probably you won't want to make work have home as a remote, so work's git-annex will not know which files home has, nor will it be able to copy files to home (but home will be able to copy files to work). +"""]] |