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>
Junio C Hamano committed
Nov 10, 2005 at 19:16 UTC
07203659d0dae619f78773d3caea6b58907a1ba5
2 files changed
+5
-5
Documentation/git-lost+found.txt
+4
-4
@@ -12,9 +12,9 @@ SYNOPSIS
12
DESCRIPTION
13
-----------
14
Finds dangling commits and tags from the object database, and
15
-creates refs to them in .git/lost+found/ directory. Commits and
16
-tags that dereference to commits go to .git/lost+found/commit
17
-and others are stored in .git/lost+found/other directory.
15
+creates refs to them in .git/lost-found/ directory. Commits and
16
+tags that dereference to commits go to .git/lost-found/commit
17
+and others are stored in .git/lost-found/other directory.
18
19
20
OUTPUT
@@ -40,7 +40,7 @@ Also you can use gitk to browse how they relate to each other
40
and existing (probably old) tags.
41
42
------------
43
-$ gitk $(cd .git/lost+found/commit && echo ??*)
43
+$ gitk $(cd .git/lost-found/commit && echo ??*)
44
------------
45
46
After making sure that it is the object you are looking for, you
git-lost+found.sh
+1
-1
@@ -2,7 +2,7 @@
2
3
. git-sh-setup || die "Not a git archive."
4
5
-laf="$GIT_DIR/lost+found"
5
+laf="$GIT_DIR/lost-found"
6
rm -fr "$laf" && mkdir -p "$laf/commit" "$laf/other" || exit
7
8
git fsck-objects |