Skip to content

Commit

Permalink
user-manual: minor rewording for clarity.
Browse files Browse the repository at this point in the history
Junio screwed up when applying the previous round of the patch;
rewording from "previous" to "old" does make the description
clearer.

Also revert the rewording from head to branch.  The description
is talking about the branch's tip commit and using the word head
is clearer.

Based on input from Sergei and Bruce.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Sergei Organov authored and Junio C Hamano committed Nov 14, 2007
1 parent fb5fd01 commit 93cbbd7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Documentation/user-manual.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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:

Expand Down

0 comments on commit 93cbbd7

Please sign in to comment.