From f22cfb5767969a2b521eadd5c2bdb4dc180ffba7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 24 Aug 2013 19:58:54 +0000 Subject: [PATCH] Added a comment --- ...comment_1_38af9b352020194e9ace34d7dde188cf._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment diff --git a/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment b/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment new file mode 100644 index 0000000000..8460300a79 --- /dev/null +++ b/doc/todo/add_metadata_to_annexed_files/comment_1_38af9b352020194e9ace34d7dde188cf._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 1" + date="2013-08-24T19:58:54Z" + content=""" +I don't know if git-annex is the right vehicle to fix this. It seems that a more generic fix that would work in non-git-annex repos would be better. + +I can answer your question though: The metadata such as urls and locations that git-annex stores in the git-annex branch is attached to objects, and not to work tree paths. +"""]]