{
    "mode": "man",
    "parameter": "GIT-PATCH-ID",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/man/GIT-PATCH-ID/json",
    "generated": "2026-10-22T13:15:10Z",
    "synopsis": "git patch-id [--stable | --unstable | --verbatim]",
    "sections": {
        "NAME": {
            "content": "git-patch-id - Compute unique ID for a patch\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "git patch-id [--stable | --unstable | --verbatim]\n\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Read a patch from the standard input and compute the patch ID for it.\n\nA \"patch ID\" is nothing but a sum of SHA-1 of the file diffs associated with a patch, with\nline numbers ignored. As such, it’s \"reasonably stable\", but at the same time also reasonably\nunique, i.e., two patches that have the same \"patch ID\" are almost guaranteed to be the same\nthing.\n\nThe main usecase for this command is to look for likely duplicate commits.\n\nWhen dealing with git diff-tree output, it takes advantage of the fact that the patch is\nprefixed with the object name of the commit, and outputs two 40-byte hexadecimal strings. The\nfirst string is the patch ID, and the second string is the commit ID. This can be used to\nmake a mapping from patch ID to commit ID.\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "",
            "subsections": [
                {
                    "name": "--verbatim",
                    "content": "Calculate the patch-id of the input as it is given, do not strip any whitespace.\n\nThis is the default if patchid.verbatim is true.\n",
                    "long": "--verbatim"
                },
                {
                    "name": "--stable",
                    "content": "Use a \"stable\" sum of hashes as the patch ID. With this option:\n\n•   Reordering file diffs that make up a patch does not affect the ID. In particular, two\npatches produced by comparing the same two trees with two different settings for\n\"-O<orderfile>\" result in the same patch ID signature, thereby allowing the computed\nresult to be used as a key to index some meta-information about the change between\nthe two trees;\n\n•   Result is different from the value produced by git 1.9 and older or produced when an\n\"unstable\" hash (see --unstable below) is configured - even when used on a diff\noutput taken without any use of \"-O<orderfile>\", thereby making existing databases\nstoring such \"unstable\" or historical patch-ids unusable.\n\n•   All whitespace within the patch is ignored and does not affect the id.\n\nThis is the default if patchid.stable is set to true.\n",
                    "long": "--stable"
                },
                {
                    "name": "--unstable",
                    "content": "Use an \"unstable\" hash as the patch ID. With this option, the result produced is\ncompatible with the patch-id value produced by git 1.9 and older and whitespace is\nignored. Users with pre-existing databases storing patch-ids produced by git 1.9 and\nolder (who do not deal with reordered patches) may want to use this option.\n\nThis is the default.\n",
                    "long": "--unstable"
                }
            ]
        },
        "GIT": {
            "content": "Part of the git(1) suite\n\nGit 2.43.0                                   07/02/2025                              GIT-PATCH-ID(1)",
            "subsections": []
        }
    },
    "summary": "git-patch-id - Compute unique ID for a patch",
    "flags": [
        {
            "flag": "",
            "long": "--verbatim",
            "arg": null,
            "description": "Calculate the patch-id of the input as it is given, do not strip any whitespace. This is the default if patchid.verbatim is true."
        },
        {
            "flag": "",
            "long": "--stable",
            "arg": null,
            "description": "Use a \"stable\" sum of hashes as the patch ID. With this option: • Reordering file diffs that make up a patch does not affect the ID. In particular, two patches produced by comparing the same two trees with two different settings for \"-O<orderfile>\" result in the same patch ID signature, thereby allowing the computed result to be used as a key to index some meta-information about the change between the two trees; • Result is different from the value produced by git 1.9 and older or produced when an \"unstable\" hash (see --unstable below) is configured - even when used on a diff output taken without any use of \"-O<orderfile>\", thereby making existing databases storing such \"unstable\" or historical patch-ids unusable. • All whitespace within the patch is ignored and does not affect the id. This is the default if patchid.stable is set to true."
        },
        {
            "flag": "",
            "long": "--unstable",
            "arg": null,
            "description": "Use an \"unstable\" hash as the patch ID. With this option, the result produced is compatible with the patch-id value produced by git 1.9 and older and whitespace is ignored. Users with pre-existing databases storing patch-ids produced by git 1.9 and older (who do not deal with reordered patches) may want to use this option. This is the default."
        }
    ],
    "examples": [],
    "see_also": []
}