From: Junio C Hamano <gitster@pobox.com>
To: Damien Robert <damien.olivier.robert+gmane@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Remove old forgotten command: whatchanged
Date: Thu, 8 Aug 2013 17:11:10 -0700 [thread overview]
Message-ID: <CAPc5daXLzM1zG-6-mfddrSywzA=P3NB5Q9kJ6uEwAy-UWmqucg@mail.gmail.com> (raw)
In-Reply-To: <ku1blo$5so$1@ger.gmane.org>
>> The above section primarily explains the use of diff-tree and it was
>> appropriate back when git-whatchanged was a script. The intent of
>> the whole document, not just this section, was to tickle the
>> curiousity of the users and encourage them to see how the above
>> "much more powerful" whatchanged was implemented by going to the
>> source.
>
> Well in this case you can say that the intent was successful since it made
> me read the source code ;)
No, it is a failure. "By going to the source" was meant for
"git-whatchanged.sh" source,
a scripted version of Porcelain, so that users can mimic what is done
in their script.
Reading C source would not help them.
next prev parent reply other threads:[~2013-08-09 0:11 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
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 [this message]
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='CAPc5daXLzM1zG-6-mfddrSywzA=P3NB5Q9kJ6uEwAy-UWmqucg@mail.gmail.com' \
--to=gitster@pobox.com \
--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).