From 917a36f9f14b11224d788fb7e9ceacfe374436ab Mon Sep 17 00:00:00 2001 From: "http://peter-simons.myopenid.com/" Date: Tue, 3 Jan 2012 18:11:40 +0000 Subject: Added a comment --- .../comment_2_73d2a015b1ac79ec99e071a8b1e29034._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/git-subtree_support__63__/comment_2_73d2a015b1ac79ec99e071a8b1e29034._comment diff --git a/doc/forum/git-subtree_support__63__/comment_2_73d2a015b1ac79ec99e071a8b1e29034._comment b/doc/forum/git-subtree_support__63__/comment_2_73d2a015b1ac79ec99e071a8b1e29034._comment new file mode 100644 index 000000000..9bac6e997 --- /dev/null +++ b/doc/forum/git-subtree_support__63__/comment_2_73d2a015b1ac79ec99e071a8b1e29034._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://peter-simons.myopenid.com/" + ip="77.188.44.113" + subject="comment 2" + date="2012-01-03T18:11:37Z" + content=""" +The point of git-subtree is that I can import another repository into sub-directory, i.e. I can have a directory called \"work\" that contains all files from the annex I have at work. If I make the other annex a remote and merge its contents, then all contents is going to be merged at the top-level, which is somewhat undesirable in my particular case. +"""]] -- cgit v1.2.3