From: John Keeping <john@keeping.me.uk>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Damien Robert <damien.olivier.robert+gmane@gmail.com>,
git@vger.kernel.org
Subject: Re: Remove old forgotten command: whatchanged
Date: Thu, 8 Aug 2013 20:09:08 +0100 [thread overview]
Message-ID: <20130808190908.GF2337@serenity.lan> (raw)
In-Reply-To: <vpqk3jwcb1q.fsf@anie.imag.fr>
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.
next prev parent reply other threads:[~2013-08-08 19:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 16:00 Remove old forgotten command: whatchanged Ramkumar Ramachandra
2013-08-07 16:51 ` Stefan Beller
2013-08-07 17:50 ` Junio C Hamano
2013-08-07 21:50 ` Stefan Beller
2013-08-08 6:39 ` Junio C Hamano
2013-08-08 4:30 ` Ramkumar Ramachandra
2013-08-08 15:03 ` Matthieu Moy
2013-08-08 15:13 ` Ramkumar Ramachandra
2013-08-08 15:24 ` Matthieu Moy
2013-08-08 17:23 ` Junio C Hamano
2013-08-09 20:01 ` [PATCH] whatchanged: document its historical nature Junio C Hamano
2013-08-09 20:14 ` John Keeping
2013-08-09 20:57 ` Junio C Hamano
2013-08-12 7:50 ` John Keeping
2013-08-13 15:56 ` Junio C Hamano
2013-08-10 7:04 ` Ramkumar Ramachandra
2013-08-08 17:51 ` Remove old forgotten command: whatchanged Damien Robert
2013-08-08 18:05 ` Ramkumar Ramachandra
2013-08-08 18:06 ` Matthieu Moy
2013-08-08 19:09 ` John Keeping [this message]
2013-08-08 19:27 ` Junio C Hamano
2013-08-09 8:29 ` Matthieu Moy
2013-08-09 17:28 ` Junio C Hamano
2013-08-13 7:58 ` Matthieu Moy
2013-08-13 16:00 ` Junio C Hamano
2013-08-08 19:19 ` Junio C Hamano
2013-08-09 0:04 ` Damien Robert
2013-08-09 0:11 ` Junio C Hamano
2013-08-07 18:01 ` Kyle J. McKay
2013-08-07 18:31 ` John Keeping
2013-08-07 18:48 ` Kyle J. McKay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130808190908.GF2337@serenity.lan \
--to=john@keeping.me.uk \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=damien.olivier.robert+gmane@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).