projects / thirdparty / git.git / blame
| Commit | Line | Data |
|---|---|---|
| 3f971fc4 JH |
1 | git-whatchanged(1) |
| 2 | ================== | |
| 3f971fc4 JH |
3 | |
| 4 | NAME | |
| 5 | ---- | |
| 7bd7f280 | 6 | git-whatchanged - Show logs with difference each commit introduces |
| 3f971fc4 JH |
7 | |
| 8 | ||
| 9 | SYNOPSIS | |
| 10 | -------- | |
| 7791a1d9 | 11 | [verse] |
| b1889c36 | 12 | 'git whatchanged' <option>... |
| 3f971fc4 JH |
13 | |
| 14 | DESCRIPTION | |
| 15 | ----------- | |
| 3f971fc4 | 16 | |
| 52f425e1 | 17 | Shows commit logs and diff output each commit introduces. |
| 3f971fc4 | 18 | |
| 52f425e1 JH |
19 | New users are encouraged to use linkgit:git-log[1] instead. The |
| 20 | `whatchanged` command is essentially the same as linkgit:git-log[1] | |
| 21 | but defaults to show the raw format diff output and to skip merges. | |
| 3f971fc4 | 22 | |
| 52f425e1 JH |
23 | The command is kept primarily for historical reasons; fingers of |
| 24 | many people who learned Git long before `git log` was invented by | |
| 25 | reading Linux kernel mailing list are trained to type it. | |
| 3f971fc4 | 26 | |
| 5348337a | 27 | |
| bd663611 LT |
28 | Examples |
| 29 | -------- | |
| 5d2fc913 | 30 | `git whatchanged -p v2.6.12.. include/scsi drivers/scsi`:: |
| bd663611 LT |
31 | |
| 32 | Show as patches the commits since version 'v2.6.12' that changed | |
| 33 | any file in the include/scsi or drivers/scsi subdirectories | |
| 34 | ||
| 6cf378f0 | 35 | `git whatchanged --since="2 weeks ago" -- gitk`:: |
| bd663611 LT |
36 | |
| 37 | Show the changes during the last two weeks to the file 'gitk'. | |
| 38 | The "--" is necessary to avoid confusion with the *branch* named | |
| 39 | 'gitk' | |
| 40 | ||
| 3f971fc4 JH |
41 | GIT |
| 42 | --- | |
| 9e1f0a85 | 43 | Part of the linkgit:git[1] suite |