updates for bare repo support

debian/changelog

@@ -10,6 +10,8 @@ git-annex (0.22) UNRELEASED; urgency=low
     option.
   * New backends: SHA512 SHA384 SHA256 SHA224
   * fsck: Check for and repair location log damage.
+  * Git annexes can now be attached to bare git repositories. Due to popular
+    demand.
 
  -- Joey Hess <joeyh@debian.org>  Sun, 13 Feb 2011 00:48:02 -0400
 

doc/bare_repositories.mdwn

@@ -1,5 +1,12 @@
 Due to popular demand, git-annex can now be used with bare repositories.
 
+So, for example, you can stash a file away in your
+repos's origin: `git annex move mybigfile --to origin`
+
+Of course, for that to work, the bare repository has to be on a system with
+[[git-annex-shell]] installed. If "origin" is on gitweb, you still can't
+use git-annex to there.
+
 **This is still an experimental feature!** 
 
 Known to work ok:

doc/bugs/bare_git_repos.mdwn

@@ -24,3 +24,6 @@ A possible other approach to the state recording repo is to not
 record state changes on the remote in that case. Git-annex already
 records remote state changes locally whenever it modifies the state of a
 remote. --[[Joey]]
+
+> And... [[done]]! See [[/bare_repositories]] for current status
+> and gotchas. --[[Joey]] 

doc/bugs/fat_support.mdwn

@@ -3,8 +3,8 @@ git-annex from being used on USB keys, that would typically
 be VFAT formatted:
 
 - Use of symlinks, which VFAT does not support. Very hard to fix.
-  One possibility is to add [[bare_git_repos]] support, then
-  a git repo on a thumb drive could be used to transfer data.
+  Instead, just use [[/bare_repositories]] on the key,
+  they're supported now.
 - Use of ":" in filenames of object files, also not supported.
   Could easily be fixed by reorganizing the object directory.
 

doc/bugs/weird_local_clone_confuses.mdwn

@@ -7,3 +7,8 @@ new cannot see origin.
 the .git/config has "url=/.../orig/.git". Apparently git is ok with that
 weird construction; probably it treats it as a bare git repo. But git-annex
 just sees a directory w/o a .git subdir, and gives up.
+
+---
+
+Just tested, and the new support for bare repositories didn't solve this.
+--[[Joey]] 

doc/git-annex.mdwn

@@ -327,10 +327,10 @@ Here are all the supported configuration settings.
   from using this remote by default. (You can still request it be used
   by the --from and --to options.)
 
-  This is, for example, useful if the remote is a bare repository,
-  which git-annex does not currently support. Or, it could be used
-  if the network connection between two repositories is too slow
-  to be used normally.
+  This is, for example, useful if the remote is located somewhere
+  without [[git-annex-shell]]. (For example, if it's on GitHub).
+  Or, it could be used if the network connection between two
+  repositories is too slow to be used normally.
 
 * `remote.<name>.annex-uuid`