git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-patch-id.txt: show that you can pipe in git-log

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Feb 16, 2011, 10:53 UTC
Message-ID
<1297853586-812-1-git-send-email-avarab@gmail.com>

Change the manual page for git-patch-id(1) to mention in the SYNOPSIS that you can pipe in the git-log(1) output.

The manual page only mentioned that you could pipe in `< patch`, I had to grep the test suite to find that you could do things like `git log -p -1 | git patch-id`.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
 Documentation/git-patch-id.txt |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt
index 4dae139..fec2cf3 100644
--- a/Documentation/git-patch-id.txt
+++ b/Documentation/git-patch-id.txt
@@ -9,6 +9,8 @@ SYNOPSIS
 --------
 'git patch-id' < <patch>
 
+'git log --pretty=format:%H -p | git patch-id'
+
 DESCRIPTION
 -----------
 A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with
-- 
1.7.2.3
Next: Junio C Hamano
Message 1 of 3 in “git-patch-id.txt: show that you can pipe in git-log”
  1. git-patch-id.txt: show that you can pipe in git-logÆvar Arnfjörð Bjarmason, Feb 16, 2011
  2. Junio C HamanoFeb 16, 2011
  3. Ævar Arnfjörð BjarmasonFeb 16, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.