On Thu, Aug 08, 2013 at 08:06:09PM +0200, Matthieu Moy wrote:
> --- a/Documentation/gitcore-tutorial.txt
> +++ b/Documentation/gitcore-tutorial.txt
> @@ -532,12 +532,7 @@ commit, and you can tell it to show a whole series of diffs.
> Alternatively, you can tell it to be "silent", and not show the diffs at
> 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.
> -
> +'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
>
> @@ -550,7 +545,7 @@ with the associated patches use the more complex (and much more
> powerful)
Isn't this paragraph slightly misleading now? We're not using a
different command any more so this could say:
which shows just the log messages, or if we want to see the log together
with the associated patches use the `--patch` option
> ----------------
> -$ git whatchanged -p
> +$ git log --raw -p
> ----------------
Then this can be "git log --patch", since it seems that the surrounding
text doesn't actually care that whatchanged prints the raw diffstat.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html