From 9a0c064be486f7bcde0932ee93b6ca52633a14c8 Mon Sep 17 00:00:00 2001 From: bremner Date: Mon, 17 Mar 2014 01:26:53 +0000 Subject: [PATCH] Added a comment: access metadata by key? --- .../comment_1_d367fdaf0425b59d694bf16059d47192._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/metadata/comment_1_d367fdaf0425b59d694bf16059d47192._comment diff --git a/doc/metadata/comment_1_d367fdaf0425b59d694bf16059d47192._comment b/doc/metadata/comment_1_d367fdaf0425b59d694bf16059d47192._comment new file mode 100644 index 0000000000..8fb93442c7 --- /dev/null +++ b/doc/metadata/comment_1_d367fdaf0425b59d694bf16059d47192._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="bremner" + ip="198.164.160.48" + subject="access metadata by key?" + date="2014-03-17T01:26:44Z" + content=""" +I'm hacking around with using metadata from an external special remote. Those work with keys, not files, so one option would be to add a GETMETADATA to the protocol. It also seems like it would not be too hard to add +an option to \"git annex metadata\" to take a key rather than a file. +"""]]