summaryrefslogtreecommitdiffstats
path: root/user-manual.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2007-11-15 00:13:36 +0000
committerJunio C Hamano <junio@hera.kernel.org>2007-11-15 00:13:36 +0000
commit8c5802d61d9a556dee3e457a8bde52a54cc636e7 (patch)
tree8ad86001f7d489a68dde56e16dd7b3d0a37e567d /user-manual.txt
parent361c1335bb152db70cab1086e3f8505e63b60354 (diff)
downloadgit-htmldocs-8c5802d61d9a556dee3e457a8bde52a54cc636e7.tar.gz
Autogenerated HTML docs for v1.5.3.5-721-g039b
Diffstat (limited to 'user-manual.txt')
-rw-r--r--user-manual.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/user-manual.txt b/user-manual.txt
index 60e13853d..c7cfbbccf 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -1367,7 +1367,7 @@ If you make a commit that you later wish you hadn't, there are two
fundamentally different ways to fix the problem:
1. You can create a new commit that undoes whatever was done
- by the previous commit. This is the correct thing if your
+ by the old commit. This is the correct thing if your
mistake has already been made public.
2. You can go back and modify the old commit. You should
@@ -1567,7 +1567,7 @@ old history using, for example,
$ git log master@{1}
-------------------------------------------------
-This lists the commits reachable from the previous version of the branch.
+This lists the commits reachable from the previous version of the head.
This syntax can be used with any git command that accepts a commit,
not just with git log. Some other examples: