update docs for --all

doc/bare_repositories.mdwn

@@ -18,6 +18,11 @@ as non-bare repositories. Except for these caveats:
   branches that have been pushed to the bare repository. So use it with care..
 * Commands that need a work tree, like `git annex add` won't work in a bare
   repository, of course.
+* However, you can (with recent versions of git-annex) run `git annex copy`,
+  `git annex get`, and `git annex move` in a bare repository. These behave
+  as if the `--all` option were used, and just operate on every single
+  version of every single file that is present in the git repository
+  history.
 
 ***
 

doc/todo/add_-all_option.mdwn

@@ -16,3 +16,7 @@ grubbing thru history to find where/when the key used to exist). So
 particular problem for `drop` and for `--auto`.
 
 --[[Joey]]
+
+> [[done]]. The .gitattributes problem was solved simply by not
+> supporting `drop --all`. `--auto` also cannot be mixed with --all for
+> similar reasons. --[[Joey]] 

doc/todo/wishlist:_support_copy_--from__61__x_--to__61__y.mdwn

@@ -17,3 +17,13 @@ But my new drive doesn't have a copy of any of the files I dropped from my deskt
 on my desktop, and then my new drive would have a copy of everything, and my desktop drive would still have plenty of space (ie the files I'd dropped to make space would still not be stored on the desktop).
 
 The git repos on these external drives are both bare (as in ``git init --bare``) because they are used only for backups. Thus I operate on them only as remotes from my main (desktop) repo.
+
+> I have now implemented the --all option, and it's the default when
+> running `git annex get` inside a bare repo.
+> 
+> So, the solution is to `cd` to the repository on old-external-drive,
+> and `git remote add newdrive /path/to/new/drive/repo`. Then run `git
+> annex copy --all --to newdrive` and it'll move everything.
+> 
+> Calling this [[done]] unless there are other use cases where the double
+> copy method is really needed? --[[Joey]]