freshlybakedca.ke
Git fork
1git-patch-id(1)
2===============
3
4NAME
5----
6git-patch-id - Compute unique ID for a patch
7
8SYNOPSIS
9--------
10[verse]
11'git patch-id' [--stable | --unstable | --verbatim]
12
13DESCRIPTION
14-----------
15Read a patch from the standard input and compute the patch ID for it.
16
17A "patch ID" is nothing but a sum of SHA-1 of the file diffs associated with a
18patch, with line numbers ignored. As such, it's "reasonably stable", but at
19the same time also reasonably unique, i.e., two patches that have the same
20"patch ID" are almost guaranteed to be the same thing.
21
22The main usecase for this command is to look for likely duplicate commits.
23
24When dealing with 'git diff-tree' output, it takes advantage of
25the fact that the patch is prefixed with the object name of the
26commit, and outputs two 40-byte hexadecimal strings. The first
27string is the patch ID, and the second string is the commit ID.
28This can be used to make a mapping from patch ID to commit ID.
29
30OPTIONS
31-------
32
33--verbatim::
34 Calculate the patch-id of the input as it is given, do not strip
35 any whitespace.
36+
37This is the default if patchid.verbatim is true.
38
39--stable::
40 Use a "stable" sum of hashes as the patch ID. With this option:
41+
42--
43- Reordering file diffs that make up a patch does not affect the ID.
44 In particular, two patches produced by comparing the same two trees
45 with two different settings for "-O<orderfile>" result in the same
46 patch ID signature, thereby allowing the computed result to be used
47 as a key to index some meta-information about the change between
48 the two trees;
49
50- Result is different from the value produced by git 1.9 and older
51 or produced when an "unstable" hash (see --unstable below) is
52 configured - even when used on a diff output taken without any use
53 of "-O<orderfile>", thereby making existing databases storing such
54 "unstable" or historical patch-ids unusable.
55
56- All whitespace within the patch is ignored and does not affect the id.
57--
58+
59This is the default if patchid.stable is set to true.
60
61--unstable::
62 Use an "unstable" hash as the patch ID. With this option,
63 the result produced is compatible with the patch-id value produced
64 by git 1.9 and older and whitespace is ignored. Users with pre-existing
65 databases storing patch-ids produced by git 1.9 and older (who do not deal
66 with reordered patches) may want to use this option.
67+
68This is the default.
69
70GIT
71---
72Part of the linkgit:git[1] suite