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 Q3 2015.

Command line used:

for f in $(grep -l '\[\[done\]\]' -- *.mdwn); do d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=09-09-2015 --pretty=oneline -- "$f")" -a -z "$(git log --since=09-09-2015 --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=09-09-2015 --pretty=oneline -- "$f")" -a -z "$(git log --since=09-09-2015 --pretty=oneline -- "$d")" ]; then git rm -- "$f"; git rm -rf "$d"; fi; done

10 files changed, 0 insertions, 154 deletions

diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment
deleted file mode 100644
index 575748b56..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.87"
- subject="comment 10"
- date="2013-12-16T20:41:47Z"
- content="""
-How is that better than `rsync -a gitrepo cleandirectory`?
-
-Perhaps better related to the original problem of getting git-annex running on a Synology NAS, [[forum/new linux arm tarball build]].
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment
deleted file mode 100644
index 1ec5bbc54..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="TroisSinges"
- ip="82.227.207.5"
- subject="comment 1"
- date="2013-11-27T14:59:11Z"
- content="""
-You could mount this NAS as a network drive on your computer (via samba for example or, even better, nfs), couldn't you? In this case you could use a real annex repository, and not a remote one.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment
deleted file mode 100644
index 89663893e..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://grossmeier.net/"
- nickname="greg"
- subject="mounting over NFS/etc ..."
- date="2013-11-27T16:01:50Z"
- content="""
-TroisSinges: Yeah, I could, but that'd limit me to being on the local network when I want to interact with the repo; not ideal.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment
deleted file mode 100644
index 60d422838..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://a-or-b.myopenid.com/"
- ip="203.45.2.230"
- subject="comment 3"
- date="2013-11-28T02:36:15Z"
- content="""
-+1 on this suggestion.
-
-Not all NASs are created equal so SAMBA/NFS isn't always the most recent version, upgrades aren't always possible (yes, I'm looking at you Drobo!) so sometimes you just can't do what g-a needs to do (locks are my big problem).
-
-This would be a great option to have, even with the downsides of losing a lot of the awesome-sauce of git-annex.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment
deleted file mode 100644
index f79fb4940..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmVICFY2CDP08xdsPr3cgmScomy9HA-1sk"
- nickname="Andrew"
- subject="comment 4"
- date="2013-11-29T04:11:24Z"
- content="""
-+1 for this style of repository (again).
-
-Presenting the content of a git-annex repository in a way that
-
-1. is transparent (nobody but me need know or care it's a git-annex repository)
-2. doesn't require installation (NAS or other device I can't install to)
-3. works without thinking (doesn't required commits or checkouts or manual deferencing symlinks - see also point 1)
-
-would fulfil the \"like dropbox but awesome\" idea from the Kickstarter.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment
deleted file mode 100644
index f87bf1aec..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 5"
- date="2013-12-05T19:52:52Z"
- content="""
-Comment #1 was my initial reaction. A regular direct mode git-annex repository on the mounted NAS share.
-
-I don't quite understand the response to it \"that'd limit me to being on the local network when I want to interact with the repo\". How could git-annex update this NAS if it's not on the local network?
-
-So far, the only reason that has been brought up that makes sense to me is locking. git-annex does use locking in its repository to prevent 2 git-annex commands run at the same time doing conflicting operations. (Lack of that locking could in some cases cause data loss.) I think git-annex's locking is limited entirely to files within the .git directory. So, if a SMB mount for a NAS does not support locking, one approach could be to move the .git directory to local disk, and use `GIT_DIR` to make it be used when operating in that repository. This should get you exactly what was requested. Whether it makes sense or is sufficiently easy to use is another question.
-
-I tend to think that a better use of a NAS in many cases is to put a directory or rsync (if it supports rsync) special remote on the NAS, and have git-annex on the individual client machines. The webapp could have a UI that makes setting up a NAS like that simple, and it would be easy to do.
-
-The use case for having a mirrored directory tree on the NAS seems to be limited to when the clients using it are something that cannot run git-annex itself, but that still cares about filenames, as opposed to just operating on file contents.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment
deleted file mode 100644
index 75614d69f..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.64"
- subject="comment 6"
- date="2013-12-05T19:57:32Z"
- content="""
-The other problem with this idea is that it seems to want the assistant to watch the file tree in the NAS, and make commits etc when files there are changed.
-
-But, any computer on the network that has the NAS mounted can change a file! AFAIK there is no interface to detect when such changes have happened; inotify does not help. It seems git-annex would have to expensively periodically scan the directory to find changes.
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment
deleted file mode 100644
index 7ff072d4c..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment
+++ /dev/null
@@ -1,28 +0,0 @@
-[[!comment format=mdwn
- username="http://grossmeier.net/"
- nickname="greg"
- subject="comment 7"
- date="2013-12-05T21:20:54Z"
- content="""
->  How could git-annex update this NAS if it's not on the local network?
-
-ssh and port forwarding, like any home server.
-
-> I tend to think that a better use of a NAS in many cases is to put a directory or rsync (if it supports rsync) special remote on the NAS, and have git-annex on the individual client machines.
-
-I'm thinking of this like the public view of a git-annex repository. I want anyone to be able to view/download the files as they normally would.
-
-> The use case for having a mirrored directory tree on the NAS seems to be limited to when the clients using it are something that cannot run git-annex itself, but that still cares about filenames, as opposed to just operating on file contents.
-
-That's exactly my use case.
-
-> So far, the only reason that has been brought up that makes sense to me is locking.
-
-Locking is actually tangential to the issue/use case. Direct mode would solve that issue, but git-annex isn't built for the Synology NAS platform, so it isn't an option.
-
-> The other problem with this idea is that it seems to want the assistant to watch the file tree in the NAS, and make commits etc when files there are changed.
-
-I think you read too much into that part. :) I only want git-annex to do things when I 'sync' or similar. I'm actually not wanting *the assistant* to do much in this case. This might even be a non-assistant applicable use case. (I don't use the assistant in my large repositories, like photos and videos and music.) I only mentioned the assistant to point out that it has some of the logic (what to do with changed/deleted files) already.
-
-And honestly, I'd be fine with an implementation that overwrote all changes on this special remote on each sync (as needed). The response to that suggestion is \"just use rsync by itself to put the files on the NAS\" but that assumes I have all of the files on my local checkout (I don't).
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment
deleted file mode 100644
index 3aeb04e53..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="gan"
- ip="85.224.8.104"
- subject="Hook implementation?"
- date="2013-12-07T01:15:46Z"
- content="""
-1. I would propose the name \"plain directory\" for this special remote.  Clean is not a good description, IMHO.
-
-2. When I read this a week ago I took the opportunity to play with the special remote hook, because as far as I can understand this could be a relatively trivial implementation that need not necessarily be in git-annex \"core\".   And I'd like to contribute back to the git-annex community and help a brother out...     I used the method of calling a single script from all hook points, and inside it look at what operation was requested.
-I didn't get that far before giving up however.  I got the feeling that hook would benefit from some extension and a bit more complete API to really create the opportunity for third-party extensions to git-annex this way.   I would prefer that the hook script can handle several instances of remotes without creating custom hook scripts for each instance.  Specifically I think a hook is needed also for \"init\" of a new remote (to get a unique identifier, and other parameters given by the user such as in this particular case, the path to the \"clean directory\")   What do you think?
-"""]]
diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment
deleted file mode 100644
index d96ac6987..000000000
--- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment
+++ /dev/null
@@ -1,35 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmicVKRM8vJX4wPuAwlLEoS2cjmFXQkjkE"
- nickname="Thomas"
- subject="pseudocode"
- date="2013-12-08T15:23:36Z"
- content="""
-The implementation should really be nothing more than the following to be run from a regular git annex repository with a configures special plain directory remote:
-
-    foreach(path : allAnnexedFiles) {
-      if(remote.exists(path) && remote.filesize(path) === expectedFilesize) goto finally;
-    
-      if(fileAvailableLocally(path)) {
-        copyFileToRemote(path);
-        goto finally;
-      }
-
-      if(shouldCopyFromElsewhere && canCopyFileFromSomeOtherRemote(path)) {
-        copyFileFromSomeOtherRemoteToRemote(path);
-      }
-
-      finally: 
-        logThatFileExistsOnRemote(path);
-    }
-    
-    foreach(remotePath : filesInRemoteDir) {
-      if(fileIsAnnexed(remotePath) || fileIsIgnored(remotePath) continue;
-    
-      delete(remotePath);
-    }
-
-The above pseude code assumes
-- that the no other process is working on the remote at the same time.
-- that the remote is not trusted.
-- that nobody expects changes done at the remote to propagate to other clones.
-"""]]