git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Remove old forgotten command: whatchanged

From
Kyle J. McKay <mackyle@gmail.com>
Date
Aug 7, 2013, 18:01 UTC
Message-ID
<4EE8B37B-F6A1-4BC4-9151-8546868E60A5@gmail.com>
In-Reply-To
<CALkWK0=zZKTwn7cdrJXsVXH-rF=xWMeD_z2XAOCnuaf2bK_h8Q@mail.gmail.com>
On Aug 7, 2013, at 09:00, Ramkumar Ramachandra wrote:
Show 32 quoted lines
> 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 use it all the time. Is there some log option to get exactly the same output? It doesn't appear that there is. The closest looks like "log --name-status" but it omits the modes and hash values.

Previous: Junio C HamanoNext: John Keeping
Message 29 of 31 in “Remove old forgotten command: whatchanged”
  1. Ramkumar RamachandraAug 7, 2013
  2. Stefan BellerAug 7, 2013
  3. Junio C HamanoAug 7, 2013
  4. Stefan BellerAug 7, 2013
  5. Junio C HamanoAug 8, 2013
  6. Ramkumar RamachandraAug 8, 2013
  7. Matthieu MoyAug 8, 2013
  8. Ramkumar RamachandraAug 8, 2013
  9. Matthieu MoyAug 8, 2013
  10. Junio C HamanoAug 8, 2013
  11. whatchanged: document its historical natureJunio C Hamano, Aug 9, 2013
  12. John KeepingAug 9, 2013
  13. Junio C HamanoAug 9, 2013
  14. John KeepingAug 12, 2013
  15. Junio C HamanoAug 13, 2013
  16. Ramkumar RamachandraAug 10, 2013
  17. Damien RobertAug 8, 2013
  18. Ramkumar RamachandraAug 8, 2013
  19. Matthieu MoyAug 8, 2013
  20. John KeepingAug 8, 2013
  21. Junio C HamanoAug 8, 2013
  22. Matthieu MoyAug 9, 2013
  23. Junio C HamanoAug 9, 2013
  24. Matthieu MoyAug 13, 2013
  25. Junio C HamanoAug 13, 2013
  26. Junio C HamanoAug 8, 2013
  27. Damien RobertAug 9, 2013
  28. Junio C HamanoAug 9, 2013
  29. Kyle J. McKayAug 7, 2013
  30. John KeepingAug 7, 2013
  31. Kyle J. McKayAug 7, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.