From: Stefan Beller <stefanbeller@googlemail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Remove old forgotten command: whatchanged
Date: Wed, 07 Aug 2013 18:51:35 +0200 [thread overview]
Message-ID: <52027B17.7040602@googlemail.com> (raw)
In-Reply-To: <CALkWK0=zZKTwn7cdrJXsVXH-rF=xWMeD_z2XAOCnuaf2bK_h8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On 08/07/2013 06:00 PM, Ramkumar Ramachandra wrote:
> Hi,
>
> This is the difference between whatchanged and log:
>
> diff --git a/whatchanged b/log
> index fa1b223..004d9aa 100644
> --- a/tmp/whatchanged
> +++ b/tmp/log
> @@ -1,4 +1,4 @@
> -int cmd_whatchanged(int argc, const char **argv, const char *prefix)
> +int cmd_log(int argc, const char **argv, const char *prefix)
> {
> struct rev_info rev;
> struct setup_revision_opt opt;
> @@ -7,13 +7,10 @@ int cmd_whatchanged(int argc, const char **argv,
> const char *prefix)
> git_config(git_log_config, NULL);
>
> init_revisions(&rev, prefix);
> - rev.diff = 1;
> - rev.simplify_history = 0;
> + rev.always_show_header = 1;
> memset(&opt, 0, sizeof(opt));
> opt.def = "HEAD";
> opt.revarg_opt = REVARG_COMMITTISH;
> cmd_log_init(argc, argv, prefix, &rev, &opt);
> - if (!rev.diffopt.output_format)
> - rev.diffopt.output_format = DIFF_FORMAT_RAW;
> return cmd_log_walk(&rev);
> }
>
> Should we remove it?
I'd deprecate it first for a year or such and remove it then.
In the meantime we could implement already remove the code
and change it to:
+ int cmd_whatchanged(int argc, const char **argv, const char *prefix)
+ {
+ return cmd_log(argc, argv, prefix)
+ }
Also we should make sure everything git whatchanged can do,
can easily be done with git log <options>.
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-08-07 16:51 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 [this message]
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
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=52027B17.7040602@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=artagnon@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).