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

[PATCH] post-receive-email: hooks.showrev: show how to include both web link and patch

From
Jim Meyering <jim@meyering.net>
Date
May 23, 2009, 12:26 UTC
Message-ID
<87fxewc8e3.fsf@meyering.net>

Add a comment showing how to include a web link (i.e. gitweb/cgit) and a patch in the email that is sent for each pushed commit. --- The quoting was tricky enough that it's worth documenting. At first I wanted to put \n\n in the printf, but to do so would have meant using \\\\n\\\\n, and in the end, the pair of "echo" statements seemed better.

FYI, I did this for glibc.git:
  http://sources.redhat.com/git/gitweb.cgi?p=glibc.git;a=summary
push-triggered messages have been sent to this list since May 21:
  http://sourceware.org/ml/glibc-cvs/2009-q2/
 contrib/hooks/post-receive-email |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
 mode change 100644 => 100755 contrib/hooks/post-receive-email
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
old mode 100644
new mode 100755
index 60cbab6..2a66063
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -44,6 +44,10 @@
 #   --pretty %s", displaying the commit id, author, date and log
 #   message.  To list full patches separated by a blank line, you
 #   could set this to "git show -C %s; echo".
+#   To list a gitweb/cgit URL *and* a full patch for each change set, use this:
+#     "t=%s; printf 'http://.../?id=%%s' \$t; echo;echo; git show -C \$t; echo"
+#   Be careful if "..." contains things that will be expanded by shell "eval"
+#   or printf.
 #
 # Notes
 # -----
--
1.6.3.1.208.gf0011
Message 1 of 1 in “post-receive-email: hooks.showrev: show how to include both web link and patch”
  1. post-receive-email: hooks.showrev: show how to include both web link and patchJim Meyering, May 23, 2009

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.