From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
Linus Torvalds <torvalds@linux-foundation.org>,
ben.knoble@gmail.com
Subject: [PATCH v2 3/3] doc: patch-id: see also git-cherry(1)
Date: Sat, 14 Feb 2026 12:55:43 +0100 [thread overview]
Message-ID: <V2_link_git-cherry.374@msgid.xyz> (raw)
In-Reply-To: <V2_CV_doc_patch-id_4.371@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
git-cherry(1) links to this command. These two commands are similar and
we also mention it in the “Examples” section now. Let’s link to it.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Documentation/git-patch-id.adoc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
index 1618994e76c..05859990c8e 100644
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -108,6 +108,10 @@ 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
--
2.53.0.26.g2afa8602a26
next prev parent reply other threads:[~2026-02-14 11:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 15:05 [PATCH 0/3] doc: patch-id: explain how to map efficiently kristofferhaugsbakk
2026-02-07 15:05 ` [PATCH 1/3] doc: patch-id: emphasize multi-patch processing kristofferhaugsbakk
2026-02-07 15:05 ` [PATCH 2/3] doc: patch-id: add script example kristofferhaugsbakk
2026-02-08 2:34 ` D. Ben Knoble
2026-02-08 17:23 ` Kristoffer Haugsbakk
2026-02-07 15:05 ` [PATCH 3/3] doc: patch-id: see also git-cherry(1) kristofferhaugsbakk
2026-02-08 2:34 ` [PATCH 0/3] doc: patch-id: explain how to map efficiently D. Ben Knoble
2026-02-14 11:55 ` [PATCH v2 " kristofferhaugsbakk
2026-02-14 11:55 ` [PATCH v2 1/3] doc: patch-id: emphasize multi-patch processing kristofferhaugsbakk
2026-02-14 11:55 ` [PATCH v2 2/3] doc: patch-id: add script example kristofferhaugsbakk
2026-02-14 11:55 ` kristofferhaugsbakk [this message]
2026-02-14 20:00 ` [PATCH v2 0/3] doc: patch-id: explain how to map efficiently Ben Knoble
2026-02-20 22:31 ` Junio C Hamano
2026-02-21 2:38 ` Ben Knoble
2026-02-23 18:04 ` Kristoffer Haugsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=V2_link_git-cherry.374@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=ben.knoble@gmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox