English ▾
Localized versions of git-whatchanged manual
Topics ▾
Email
Latest version
▾
git-whatchanged last updated in 2.43.0
Changes in the git-whatchanged manual
Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.43.1 → 2.47.1 no changes
- 2.43.0 11/20/23
- 2.1.4 → 2.42.3 no changes
- 2.0.5 12/17/14
DESCRIPTION
Shows commit logs and diff output each commit introduces.
New users are encouraged to use git-log[1] instead. The
whatchanged
command is essentially the same as git-log[1]
but defaults to showing the raw format diff output and skipping 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 git[1] suite