diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-07-15 22:24:45 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-07-15 22:24:45 +0000 |
| commit | 78e3a7820b2267111cd2f29fd3d06e8919f2b36c (patch) | |
| tree | e5eb61d417f8655688f52d01beeddb01b9503560 /user-manual.txt | |
| parent | 635553978d5d3414c3d9699aa009ae29839356ab (diff) | |
| download | git-htmldocs-78e3a7820b2267111cd2f29fd3d06e8919f2b36c.tar.gz | |
Autogenerated HTML docs for v1.7.2-rc3-39-g53b30
Diffstat (limited to 'user-manual.txt')
| -rw-r--r-- | user-manual.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/user-manual.txt b/user-manual.txt index fe6fb722d..22aee34d4 100644 --- a/user-manual.txt +++ b/user-manual.txt @@ -397,7 +397,7 @@ is usually a shortcut for the HEAD branch in the repository "origin". For the complete list of paths which git checks for references, and the order it uses to decide which to choose when there are multiple references with the same shorthand name, see the "SPECIFYING -REVISIONS" section of linkgit:git-rev-parse[1]. +REVISIONS" section of linkgit:gitrevisions[1]. [[Updating-a-repository-With-git-fetch]] Updating a repository with git fetch @@ -568,7 +568,7 @@ We have seen several ways of naming commits already: - HEAD: refers to the head of the current branch There are many more; see the "SPECIFYING REVISIONS" section of the -linkgit:git-rev-parse[1] man page for the complete list of ways to +linkgit:gitrevisions[1] man page for the complete list of ways to name revisions. Some examples: ------------------------------------------------- @@ -909,7 +909,7 @@ commits reachable from some head but not from any tag in the repository: $ gitk $( git show-ref --heads ) --not $( git show-ref --tags ) ------------------------------------------------- -(See linkgit:git-rev-parse[1] for explanations of commit-selecting +(See linkgit:gitrevisions[1] for explanations of commit-selecting syntax such as `--not`.) [[making-a-release]] @@ -1635,7 +1635,7 @@ you've checked out. The reflogs are kept by default for 30 days, after which they may be pruned. See linkgit:git-reflog[1] and linkgit:git-gc[1] to learn how to control this pruning, and see the "SPECIFYING REVISIONS" -section of linkgit:git-rev-parse[1] for details. +section of linkgit:gitrevisions[1] for details. Note that the reflog history is very different from normal git history. While normal history is shared by every repository that works on the |