mirror of
https://github.com/git/git.git
synced 2026-01-11 13:23:12 +09:00
3f051fc9c9
The default `--unstable` is a legacy format that predates `--stable`.
That’s why 2871f4d4 (builtin: patch-id: add --verbatim as a command mode,
2022-10-24) made `--verbatim` lock in[1] `--stable`:
Users of --unstable mainly care about compatibility with old git
versions, which unstripping the whitespace would break. Thus there
isn't a usecase for the combination of --verbatim and --unstable,
and we don't expose this so as to not add maintainence burden.
† 1: imply `--stable`, disallow `--unstable`
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
73 lines
2.4 KiB
Plaintext
73 lines
2.4 KiB
Plaintext
git-patch-id(1)
|
|
===============
|
|
|
|
NAME
|
|
----
|
|
git-patch-id - Compute unique ID for a patch
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[synopsis]
|
|
git patch-id [--stable | --unstable | --verbatim]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Read a patch from the standard input and compute the patch ID for it.
|
|
|
|
A "patch ID" is nothing but a sum of SHA-1 of the file diffs associated with a
|
|
patch, with line numbers ignored. As such, it's "reasonably stable", but at
|
|
the same time also reasonably unique, i.e., two patches that have the same
|
|
"patch ID" are almost guaranteed to be the same thing.
|
|
|
|
The main usecase for this command is to look for likely duplicate commits.
|
|
|
|
When dealing with `git diff-tree --patch` output, it takes advantage of
|
|
the fact that the patch is prefixed with the object name of the
|
|
commit, and outputs two 40-byte hexadecimal strings. The first
|
|
string is the patch ID, and the second string is the commit ID.
|
|
This can be used to make a mapping from patch ID to commit ID.
|
|
|
|
OPTIONS
|
|
-------
|
|
|
|
`--verbatim`::
|
|
Calculate the patch ID of the input as it is given, do not strip
|
|
any whitespace. Implies `--stable` and forbids `--unstable`.
|
|
+
|
|
This is the default if `patchid.verbatim` is `true`.
|
|
|
|
`--stable`::
|
|
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.
|
|
|
|
- The 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`.
|
|
|
|
`--unstable`::
|
|
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.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|