projects / thirdparty / git.git / blame
| Commit | Line | Data |
|---|---|---|
| 7fc9d69f JH |
1 | git-patch-id(1) |
| 2 | =============== | |
| 3 | ||
| 4 | NAME | |
| 5 | ---- | |
| c3f0baac | 6 | git-patch-id - Compute unique ID for a patch |
| 7fc9d69f JH |
7 | |
| 8 | SYNOPSIS | |
| 9 | -------- | |
| b1889c36 | 10 | 'git patch-id' < <patch> |
| 7fc9d69f JH |
11 | |
| 12 | DESCRIPTION | |
| 13 | ----------- | |
| 52a22d1e LAS |
14 | A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with |
| 15 | whitespace and line numbers ignored. As such, it's "reasonably stable", but at | |
| abda1ef5 | 16 | the same time also reasonably unique, i.e., two patches that have the same "patch |
| 52a22d1e | 17 | ID" are almost guaranteed to be the same thing. |
| 7fc9d69f | 18 | |
| 52a22d1e | 19 | IOW, you can use this thing to look for likely duplicate commits. |
| 7fc9d69f | 20 | |
| a77a9222 JH |
21 | When dealing with git-diff-tree output, it takes advantage of |
| 22 | the fact that the patch is prefixed with the object name of the | |
| 23 | commit, and outputs two 40-byte hexadecimal string. The first | |
| 24 | string is the patch ID, and the second string is the commit ID. | |
| 25 | This can be used to make a mapping from patch ID to commit ID. | |
| 26 | ||
| 7fc9d69f JH |
27 | OPTIONS |
| 28 | ------- | |
| 52a22d1e LAS |
29 | <patch>:: |
| 30 | The diff to create the ID of. | |
| 7fc9d69f JH |
31 | |
| 32 | Author | |
| 33 | ------ | |
| 34 | Written by Linus Torvalds <torvalds@osdl.org> | |
| 35 | ||
| 36 | Documentation | |
| 37 | -------------- | |
| 38 | Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. | |
| 39 | ||
| 40 | GIT | |
| 41 | --- | |
| 9e1f0a85 | 42 | Part of the linkgit:git[1] suite |