5a31252702
There have been quite a few `--i-still-use-this` user reports since Git
2.51.0 was released.[1][2] And it doesn’t seem like they are reading
the man page about the git-log(1) equivalent.
Tell them what options to plug into git-log(1), either as a replacement
command or as an alias.[3] That template produces almost the same
output[4] and is arguably a plug-in replacement. Concretely, add
an optional `hint` argument so that we can use it right after the
initial error line.
Also mention the same concrete options in the documentation while we’re
at it.
[1]: E.g.,
• https://lore.kernel.org/git/e1a69dea-bcb6-45fc-83d3-9e50d32c410b@5y5.one/
• https://lore.kernel.org/git/1011073f-9930-4360-a42f-71eb7421fe3f@chrispalmer.uk/#t
• https://lore.kernel.org/git/9fcbfcc4-79f9-421f-b9a4-dc455f7db485@acm.org/#t
• https://lore.kernel.org/git/83241BDE-1E0D-489A-9181-C608E9FCC17B@gmail.com/
[2]: The error message on 2.51.0 does tell them to report it, unconditionally
[3]: We allow aliasing deprecated builtins now for people who are very
used to the command name or just like it a lot
[4]: You only get different outputs if you happen to have empty
commits (no changes)[4]
[5]: https://lore.kernel.org/git/20250825085428.GA367101@coredump.intra.peff.net/
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
54 lines
1.3 KiB
Plaintext
54 lines
1.3 KiB
Plaintext
git-whatchanged(1)
|
|
==================
|
|
|
|
NAME
|
|
----
|
|
git-whatchanged - Show logs with differences each commit introduces
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[synopsis]
|
|
git whatchanged <option>...
|
|
|
|
WARNING
|
|
-------
|
|
`git whatchanged` has been deprecated and is scheduled for removal in
|
|
a future version of Git, as it is merely `git log` with different
|
|
default; `whatchanged` is not even shorter to type than `log --raw`.
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
Shows commit logs and diff output each commit introduces.
|
|
|
|
New users are encouraged to use linkgit:git-log[1] instead. The
|
|
`whatchanged` command is essentially the same as linkgit:git-log[1]
|
|
but defaults to showing the raw format diff output and skipping merges:
|
|
|
|
----
|
|
git log --raw --no-merges
|
|
----
|
|
|
|
The command is primarily kept for historical reasons; fingers of
|
|
many people who learned Git long before `git log` was invented by
|
|
reading the Linux kernel mailing list are trained to type it.
|
|
|
|
|
|
Examples
|
|
--------
|
|
`git whatchanged -p v2.6.12.. include/scsi drivers/scsi`::
|
|
|
|
Show as patches the commits since version 'v2.6.12' that changed
|
|
any file in the include/scsi or drivers/scsi subdirectories
|
|
|
|
`git whatchanged --since="2 weeks ago" -- gitk`::
|
|
|
|
Show the changes during the last two weeks to the file 'gitk'.
|
|
The "--" is necessary to avoid confusion with the *branch* named
|
|
'gitk'
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|