aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2026-03-02 17:06:53 -0800
committerJunio C Hamano <gitster@pobox.com>2026-03-02 17:06:53 -0800
commit34113149cfde760b6b791939c6d8d87d27ca2767 (patch)
tree5a012ba1839864c5a96b261c45cfacc60dddaa1c
parent427d39ca4f4f7a0e66652d92340af43cbda5135e (diff)
parented84bc1c0da0c5a972459f639801bc7ec235084c (diff)
downloadgit-34113149cfde760b6b791939c6d8d87d27ca2767.tar.xz
Merge branch 'kh/doc-patch-id-4'
Doc update. * kh/doc-patch-id-4: doc: patch-id: see also git-cherry(1) doc: patch-id: add script example doc: patch-id: emphasize multi-patch processing
-rw-r--r--Documentation/git-patch-id.adoc51
1 files changed, 48 insertions, 3 deletions
diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
index 013e1a6190..05859990c8 100644
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -3,7 +3,7 @@ git-patch-id(1)
NAME
----
-git-patch-id - Compute unique ID for a patch
+git-patch-id - Compute unique IDs for patches
SYNOPSIS
--------
@@ -12,7 +12,7 @@ git patch-id [--stable | --unstable | --verbatim]
DESCRIPTION
-----------
-Read a patch from the standard input and compute the patch ID for it.
+Read patches from standard input and compute the patch IDs.
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
@@ -25,7 +25,8 @@ 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.
+This can be used to make a mapping from patch ID to commit ID for a
+set or range of commits.
OPTIONS
-------
@@ -67,6 +68,50 @@ This is the default if `patchid.stable` is set to `true`.
+
This is the default.
+EXAMPLES
+--------
+
+linkgit:git-cherry[1] shows what commits from a branch have patch ID
+equivalent commits in some upstream branch. But it only tells you
+whether such a commit exists or not. What if you wanted to know the
+relevant commits in the upstream? We can use this command to make a
+mapping between your branch and the upstream branch:
+
+----
+#!/bin/sh
+
+upstream="$1"
+branch="$2"
+test -z "$branch" && branch=HEAD
+limit="$3"
+if test -n "$limit"
+then
+ tail_opts="$limit".."$upstream"
+else
+ since=$(git log --format=%aI "$upstream".."$branch" | tail -1)
+ tail_opts=--since="$since"' '"$upstream"
+fi
+for_branch=$(mktemp)
+for_upstream=$(mktemp)
+
+git rev-list --no-merges "$upstream".."$branch" |
+ git diff-tree --patch --stdin |
+ git patch-id --stable | sort >"$for_branch"
+git rev-list --no-merges $tail_opts |
+ git diff-tree --patch --stdin |
+ git patch-id --stable | sort >"$for_upstream"
+join -a1 "$for_branch" "$for_upstream" | cut -d' ' -f2,3
+rm "$for_branch"
+rm "$for_upstream"
+----
+
+Now the first column shows the commit from your branch and the second
+column shows the patch ID equivalent commit, if it exists.
+
+SEE ALSO
+--------
+linkgit:git-cherry[1]
+
GIT
---
Part of the linkgit:git[1] suite