Documentation: minor edits of git-lost-found manpage
Minor improvements to grammar and clarity of lost-found manpage. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu> Signed-off-by: Junio C Hamano <junkio@cox.net>
J. Bruce Fields committed
Apr 16, 2007 at 00:37 UTC
cb1881c6eeb021102a7a0ae87dbddfd52bf1f04f
1 file changed
+11
-12
Documentation/git-lost-found.txt
+11
-12
@@ -12,23 +12,22 @@ 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 the .git/lost-found/ directory. Commits and
16
+tags that dereference to commits are stored in .git/lost-found/commit,
17
+and other objects are stored in .git/lost-found/other.
18
19
20
OUTPUT
21
------
22
-One line description from the commit and tag found along with
23
-their object name are printed on the standard output.
24
-
22
+Prints to standard output the object names and one-line descriptions
23
+of any commits or tags found.
24
25
EXAMPLE
26
-------
27
29
-Suppose you run 'git tag -f' and mistyped the tag to overwrite.
28
+Suppose you run 'git tag -f' and mistype the tag to overwrite.
29
The ref to your tag is overwritten, but until you run 'git
31
-prune', it is still there.
30
+prune', the tag itself is still there.
31
32
------------
33
$ git lost-found
@@ -36,15 +35,15 @@ $ git lost-found
35
...
36
------------
37
39
-Also you can use gitk to browse how they relate to each other
40
-and existing (probably old) tags.
38
+Also you can use gitk to browse how any tags found relate to each
39
+other.
40
41
------------
42
$ gitk $(cd .git/lost-found/commit && echo ??*)
43
------------
44
46
-After making sure that it is the object you are looking for, you
47
-can reconnect it to your regular .git/refs hierarchy.
45
+After making sure you know which the object is the tag you are looking
46
+for, you can reconnect it to your regular .git/refs hierarchy.
47
48
------------
49
$ git cat-file -t 1ef2b196