remove old closed bugs and todo items to speed up wiki updates and reduce size

Remove closed bugs and todos that were last edited or commented before 2017.

Command line used:

for f in $(grep -l '|done\]\]' -- *.mdwn); do d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2017 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2017 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; done
for f in $(grep -l '\[\[done\]\]' -- *.mdwn); do d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2017 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2017 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; done

4 files changed, 0 insertions, 74 deletions

diff --git a/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment b/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment
deleted file mode 100644
index 54cbe6fa6..000000000
--- a/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 1"""
- date="2016-02-19T19:18:41Z"
- content="""
-The metadata command is pretty complex. A batch interface would need to
-cover both setting and getting. 
-
-There are four different ways to change a value, so it would probably
-make sense for the input to be of the form "file field=value"
-or "file field+=value" or "file field-=value" or "file field?=value"
-
-A field can have multiple values, including "". So, a batch interface
-to querying the value would need to handle that in its output. Perhaps
-json output?
-"""]]
diff --git a/doc/todo/metadata_--batch/comment_2_6230fe7d6a7b6156b74b7f4e3641c200._comment b/doc/todo/metadata_--batch/comment_2_6230fe7d6a7b6156b74b7f4e3641c200._comment
deleted file mode 100644
index 5b39175a9..000000000
--- a/doc/todo/metadata_--batch/comment_2_6230fe7d6a7b6156b74b7f4e3641c200._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4"
- subject="comment 2"
- date="2016-02-19T20:06:19Z"
- content="""
-yes -- json output would probably be the best
-I know that other --batch functions do not take json input, but I wonder if it might make sense here as well? smth like {'file': 'filename', 'add-field': {'field1': 'value1'}, 'remove-field': ..., 'add-tag': ['tag1', 'tag2'], 'remove-tag': ['...     and so on.
-"""]]
diff --git a/doc/todo/metadata_--batch/comment_3_23c88eab56628fd2f75aceb21f59992e._comment b/doc/todo/metadata_--batch/comment_3_23c88eab56628fd2f75aceb21f59992e._comment
deleted file mode 100644
index 38dcd7d8c..000000000
--- a/doc/todo/metadata_--batch/comment_3_23c88eab56628fd2f75aceb21f59992e._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 3"""
- date="2016-02-19T20:47:28Z"
- content="""
-See
-<http://git-annex.branchable.com/todo/ability_to_set_metadata_from_json/>
-
-If it does support json input, the simplest interface would be to use the
-same json objects for both output and input.
-
-Both aeson and json are currently dependencies, and either could be used to
-parse json input.
-"""]]
diff --git a/doc/todo/metadata_--batch/comment_4_c72eb16b630b200265e125ebaf7d0d36._comment b/doc/todo/metadata_--batch/comment_4_c72eb16b630b200265e125ebaf7d0d36._comment
deleted file mode 100644
index 4cd0f2d34..000000000
--- a/doc/todo/metadata_--batch/comment_4_c72eb16b630b200265e125ebaf7d0d36._comment
+++ /dev/null
@@ -1,36 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 4"""
- date="2016-07-25T17:39:37Z"
- content="""
---batch mode should be usable to get current metadata, set new
-metadata, and remove existing metadata. The non-batch metadata command has
-different syntaxes for all of these, but it would be good to have a single
-interface that handles all three in batch mode.
-
-It could read a line containing the file or key, with any metadata
-fields that should be changed:
-
-	{"file":"foo"}
-	{"file":"foo","author":["bar"]}
-	{"key":"SHA...","author":[]}
-
-And reply with *all* the metadata, in nearly the same format:
-
-	{"file":"foo","key":"SHA...","author":["bar"],lastchanged:["date"],"success":true}
-
-And that reply could in turn be edited and fed back in to change the
-metadata.
-
-----
-
-There's a DRY problem here because there's the current JSON generator code,
-and I'd have to add an Aeson parser to parse the JSON input. But, Aeson
-parsers also automatically have a matching generator, which is guaranteed
-to generate code that the parser can parse.
-
-So, it would be nice to use the Aeson JSON generator, instead of the
-current one, but that can only be done if the JSON is formatted the same,
-or close enough that nothing currently consuming `metadata --json` will
-break.
-"""]]