diff options
| author | Jon Loeliger <jdl@freescale.org> | 2005-09-22 10:51:57 -0500 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-09-22 18:31:14 -0700 |
| commit | d154dcc8b62ff609a0a3b271e1665c53df5c06a5 (patch) | |
| tree | 5dc7e4312a5d4f2bb47adb55eef0da9d6e4ec9e7 /Documentation | |
| parent | c8b48ba4767ff9da19ef4f41f8d870f11742d833 (diff) | |
| download | git-d154dcc8b62ff609a0a3b271e1665c53df5c06a5.tar.gz | |
[PATCH] Retitle 'inspecting what happened' section.
In the tutorial, there is a section entitled "Checking it out"
that shows how to use diff log and whatchanged to insect some
of the repository state.
As the phrase "checkout" ususally carries some baggage WRT
other revision control mechanism, I suggest that we re-title
this section something like "Inspecting Changes".
Signed-off-by: Jon Loeliger <jdl@freescale.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/tutorial.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt index 307cc07919..36f42e051c 100644 --- a/Documentation/tutorial.txt +++ b/Documentation/tutorial.txt @@ -432,8 +432,8 @@ message headers, and a few one-liners that actually do the commit itself (`git-commit`). -Checking it out ---------------- +Inspecting Changes +------------------ While creating changes is useful, it's even more useful if you can tell later what changed. The most useful command for this is another of the |