From 66fc77a27dc6824f0fb3c911cb5f8535afefea4b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 1 May 2015 15:41:49 -0400 Subject: [PATCH] followup --- ...nt_4_237721c5e8f66f303a1828810573a23d._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment diff --git a/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment b/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment new file mode 100644 index 0000000000..d2c13888e1 --- /dev/null +++ b/doc/metadata/comment_4_237721c5e8f66f303a1828810573a23d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2015-05-01T19:38:36Z" + content=""" +@madduck, you could file a todo if you want about that. + +However, I have my doubts; if the json supposed to include the full set of +metadata for the file? If so, that seems a potentially expensive interface. +If not, it would be hard to tell when metadata should be deleted, or when +multiple values are being set, vs a value being changed. + +The current interface to set metadata deals with these possibilities in a +compact and sensible way. +"""]]