From e8420c3b7d04bcad1a4a0d275cb831066cad1fdc Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 5 Sep 2012 19:56:06 +0000 Subject: [PATCH] Added a comment --- .../comment_1_96beb9ea895c80285748adb940b4f57d._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/multiple_sym_links___40__for_tagging_photos__41____63__/comment_1_96beb9ea895c80285748adb940b4f57d._comment diff --git a/doc/forum/multiple_sym_links___40__for_tagging_photos__41____63__/comment_1_96beb9ea895c80285748adb940b4f57d._comment b/doc/forum/multiple_sym_links___40__for_tagging_photos__41____63__/comment_1_96beb9ea895c80285748adb940b4f57d._comment new file mode 100644 index 0000000000..b4d2433aa3 --- /dev/null +++ b/doc/forum/multiple_sym_links___40__for_tagging_photos__41____63__/comment_1_96beb9ea895c80285748adb940b4f57d._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.236" + subject="comment 1" + date="2012-09-05T19:56:06Z" + content=""" +I'd recommend linking to the annexed file. Which is what `cp -a` does BTW. Then it'll just be a peice of content that is used by more than one filename, which git-annex handles well. However, if you then edited +one file, git-annex would not update the other link to point to the new content. +"""]]