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

9 files changed, 0 insertions, 108 deletions

diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_1_5c8812973cf91b046e7fc44d7e86c78e._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_1_5c8812973cf91b046e7fc44d7e86c78e._comment
deleted file mode 100644
index 61d82e2ae..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_1_5c8812973cf91b046e7fc44d7e86c78e._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.48"
- subject="comment 1"
- date="2013-07-17T23:23:50Z"
- content="""
-I'm interested to hear that your team is using git-annex.
-
-Have you tried `git config annex.alwayscommit false`? This will avoid committing, and just store the info in a local journal -- so even `git annex fsck` will still work.
-
-Hmm, perhaps you want to update the branch when running `git annex copy` to put files onto the server, but not when getting them? A switch to disable updating the branch would then make sense. Any use of fsck would notice the inconsistency though, and commit a fix to the git-annex branch -- unless you also used the new switch when running fsck.
-
-But what happens if someone makes a change, pushes to the server, but forgets to `git annex copy` the file? Everyone would then be left with a missing file that git annex doesn't know where it is. One of the reasons it tracks the locations is so that if necessary you know which repository such a misplaced fail is stored in. And can go track down that person's laptop and apply a cluebat. ;) Do you do something on the server to prevent this scenario?
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_2_f36b6a5b128423211aac91a252ecf85f._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_2_f36b6a5b128423211aac91a252ecf85f._comment
deleted file mode 100644
index 3379742d2..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_2_f36b6a5b128423211aac91a252ecf85f._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="http://caust1c.myopenid.com/"
- nickname="asbraithwaite"
- subject="comment 2"
- date="2013-07-17T23:42:25Z"
- content="""
-What would happen if we wanted to copy a file to the server 
-with that set? or even when running `git annex add`
-You understood me exactly though.
-We'd like to be able to get the files without a commit, but copy them 
-with a commit of the changes.
-The way we operate, if somebody makes a change with regards to 
-largefiles, they should also add a test for it.
-Ideally, the test suite would catch it.  That or people would 
-realize that theres a new big file and send around an email to 
-see who was trying to a largefile when they couldn't reach it.
-
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_3_ad1569b2405acacd2e37f42b82f24c88._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_3_ad1569b2405acacd2e37f42b82f24c88._comment
deleted file mode 100644
index 14ab5f65a..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_3_ad1569b2405acacd2e37f42b82f24c88._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.6.48"
- subject="comment 3"
- date="2013-07-18T00:12:39Z"
- content="""
-Actually, when a file is sent to a git repository on the server, it will update the location log on that side. So even if the client has alwayscommit=false, other clients will learn the file has reached the server.
-
-So that might just work for you.
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_4_8aba90150fe178ce9712ad951628f3d6._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_4_8aba90150fe178ce9712ad951628f3d6._comment
deleted file mode 100644
index c1f148fdb..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_4_8aba90150fe178ce9712ad951628f3d6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="comment 4"
- date="2013-07-18T18:03:00Z"
- content="""
-If you can have developers only add large files on the central server, avoiding using git annex sync and only pulling from git repo should work, I think.
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_5_6f42d240e0021f4dfa37146bea3f5d7e._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_5_6f42d240e0021f4dfa37146bea3f5d7e._comment
deleted file mode 100644
index aa547d790..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_5_6f42d240e0021f4dfa37146bea3f5d7e._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://caust1c.myopenid.com/"
- nickname="asbraithwaite"
- subject="comment 5"
- date="2013-07-18T21:17:45Z"
- content="""
-Wow.  This worked better than expected.  I'm still trying to understand the implementation (I'm not familiar with Haskell), but there is some magic going on.
-
-To explain:
-
-I didn't expect that when I added a file (Locally and to the annex remote) that when somebody else did a pull, git-annex would recognize this and update the working copy to download and include that file.
-
-I'm not sure if this is intended behavior or not (since I thought all commands had to go through git-annex) but I like it nonetheless.
-
-Thanks again for the tips!
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_6_5fda455febf728b079f26fe42bf7bcab._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_6_5fda455febf728b079f26fe42bf7bcab._comment
deleted file mode 100644
index 3f10e48ad..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_6_5fda455febf728b079f26fe42bf7bcab._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://caust1c.myopenid.com/"
- nickname="asbraithwaite"
- subject="comment 6"
- date="2013-07-18T21:23:58Z"
- content="""
-Disregard that.  I was testing it with a particular file that didn't exactly play nice.
-
-Basically, to test this before production I used `dd bs=1024 count=100000 if=/dev/zero of=bigfile`.
-
-When I did a `git pull`, it showed the symlink as being valid.
-
-When I changed the command to `dd bs=1024 count=100000 if=/dev/urandom of=bigfile` then it showed the symlink as bad after pulling.
-
-Weird!
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_7_f1052ab997f1a2cccbabfd1533fc0a59._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_7_f1052ab997f1a2cccbabfd1533fc0a59._comment
deleted file mode 100644
index deb25a9ce..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_7_f1052ab997f1a2cccbabfd1533fc0a59._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog"
- nickname="Michael"
- subject="comment 7"
- date="2013-07-18T21:48:06Z"
- content="""
-If you wanted to auto-get files on git pull, you could trying putting git annex get into .git/hooks/post-merge (needs to be marked as executable).
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_8_07804647b6023436878756bd97a23f32._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_8_07804647b6023436878756bd97a23f32._comment
deleted file mode 100644
index 4901a2d97..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_8_07804647b6023436878756bd97a23f32._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="4.154.0.140"
- subject="comment 8"
- date="2013-07-20T20:07:53Z"
- content="""
-`dd bs=1024 count=100000 if=/dev/zero of=bigfile` obviously creates the same data each time, so if that same size empty file has previously been in a repository, and the content is still present there, the symlink will automatically point to it when it gets added. In other words, git-annex performs automatic deduplication of file contents, and so it was able to save you a download in this case.
-"""]]
diff --git a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_9_fdc883d3963de8072794f3189742e4e3._comment b/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_9_fdc883d3963de8072794f3189742e4e3._comment
deleted file mode 100644
index 2287f6935..000000000
--- a/doc/todo/wishlist__58_____34__quiet__34___annex_get_for_centralized_use_case/comment_9_fdc883d3963de8072794f3189742e4e3._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.227"
- subject="comment 9"
- date="2014-01-02T17:25:50Z"
- content="""
-I have now implemented a way to mark a remote as readonly. This prevents git-annex from pushing anything to the remote, or modifying it in other ways.
-
-It seems that in your use case, you might want to avoid git-annex sync pushing the git-annex branch, but still push a branch like master. So far, it's up to you to decide which branches to manually push; readonly disables all pushing.
-"""]]