Rename .git/lost+found to .git/lost-found.

Just to avoid confusion that scripts poorly written by somebody
else ;-) might mistake this as a mount point, or backup tools
ignoring the directory.  The latter is probably not a big loss,
however, considering that this directory's contents are to be
used while fresh anyway.

Signed-off-by: Junio C Hamano <junkio@cox.net>

Documentation/git-lost+found.txt

@@ -12,9 +12,9 @@ SYNOPSIS
 DESCRIPTION
 -----------
 Finds dangling commits and tags from the object database, and
-creates refs to them in .git/lost+found/ directory.  Commits and
-tags that dereference to commits go to .git/lost+found/commit
-and others are stored in .git/lost+found/other directory.
+creates refs to them in .git/lost-found/ directory.  Commits and
+tags that dereference to commits go to .git/lost-found/commit
+and others are stored in .git/lost-found/other directory.
 
 
 OUTPUT
@@ -40,7 +40,7 @@ Also you can use gitk to browse how they relate to each other
 and existing (probably old) tags.
 
 ------------
-$ gitk $(cd .git/lost+found/commit && echo ??*)
+$ gitk $(cd .git/lost-found/commit && echo ??*)
 ------------
 
 After making sure that it is the object you are looking for, you

git-lost+found.sh

@@ -2,7 +2,7 @@
 
 . git-sh-setup || die "Not a git archive."
 
-laf="$GIT_DIR/lost+found"
+laf="$GIT_DIR/lost-found"
 rm -fr "$laf" && mkdir -p "$laf/commit" "$laf/other" || exit
 
 git fsck-objects |