summaryrefslogtreecommitdiffstats
path: root/user-manual.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-02-02 07:35:15 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-02-02 07:35:15 +0000
commit39381a7c839f85e6b5380251ecffcd5b1a214945 (patch)
treedf3e49a3381f4e02410c0c84dae63a1b28db65c4 /user-manual.txt
parent8f62db9398f1b5c51907cea20d4b51cb0cd391d3 (diff)
downloadgit-htmldocs-39381a7c839f85e6b5380251ecffcd5b1a214945.tar.gz
Autogenerated HTML docs for v1.5.0-rc3-16-gaacd
Diffstat (limited to 'user-manual.txt')
-rw-r--r--user-manual.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/user-manual.txt b/user-manual.txt
index b6916d11b..6576625fa 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -398,7 +398,7 @@ branch name, but this longer name can also be useful. Most
importantly, it is a globally unique name for this commit: so if you
tell somebody else the object name (for example in email), then you are
guaranteed that name will refer to the same commit in their repository
-that you it does in yours (assuming their repository has that commit at
+that it does in yours (assuming their repository has that commit at
all).
Understanding history: commits, parents, and reachability
@@ -617,7 +617,7 @@ the relationships between these snapshots.
Git provides extremely flexible and fast tools for exploring the
history of a project.
-We start with one specialized tool which is useful for finding the
+We start with one specialized tool that is useful for finding the
commit that introduced a bug into a project.
How to use bisect to find a regression
@@ -1492,7 +1492,7 @@ dangling commit 13472b7c4b80851a1bc551779171dcb03655e9b5
...
-------------------------------------------------
-and watch for output that mentions "dangling commits". You can examine
+You can examine
one of those dangling commits with, for example,
------------------------------------------------
@@ -2923,6 +2923,8 @@ Think about how to create a clear chapter dependency graph that will
allow people to get to important topics without necessarily reading
everything in between.
+Say something about .gitignore.
+
Scan Documentation/ for other stuff left out; in particular:
howto's
some of technical/?