Junio C Hamano <gits...@pobox.com> writes: > It is meant to teach them "if you want to do your own 'git log', you > can do so with 'rev-list' piped to 'diff-tree --stdin'". Changing > 'whatchanged' to 'log' in the latter statement is an improvement, > but dropping 'can be done by combining rev-list and diff-tree' goes > against the objective of the whole document.
Then, we can keep the "In fact, together with the 'git rev-list' program ..." sentence, but drop "A trivial (but very useful) script ...", which is both technically incorrect (whatchanged is not a script anymore) and misleading because it advertises whatchanged. That would look like this: diff --git a/Documentation/git.txt b/Documentation/git.txt index 3bdd56e..486a58b 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -818,7 +818,7 @@ for further details. 'GIT_FLUSH':: If this environment variable is set to "1", then commands such as 'git blame' (in incremental mode), 'git rev-list', 'git log', - 'git check-attr', 'git check-ignore', and 'git whatchanged' will + 'git check-attr', and 'git check-ignore' will force a flush of the output stream after each record have been flushed. If this variable is set to "0", the output of these commands will be done diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt index f538a87..8e53560 100644 --- a/Documentation/gitcore-tutorial.txt +++ b/Documentation/gitcore-tutorial.txt @@ -534,9 +534,8 @@ all, but just show the actual commit message. In fact, together with the 'git rev-list' program (which generates a list of revisions), 'git diff-tree' ends up being a veritable fount of -changes. A trivial (but very useful) script called 'git whatchanged' is -included with Git which does exactly this, and shows a log of recent -activities. +changes. The porcelain command 'git log' can also be used to display +changes introduced by some commits. To see the whole history of our pitiful little git-tutorial project, you can do @@ -546,11 +545,10 @@ $ git log ---------------- which shows just the log messages, or if we want to see the log together -with the associated patches use the more complex (and much more -powerful) +with the associated patches, use the `--patch` option: ---------------- -$ git whatchanged -p +$ git log -p ---------------- and you will see exactly what has changed in the repository over its -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html