From: "Eric Mertens" <emertens@gmail.com>
To: git@vger.kernel.org
Subject: Correction for post-receive-email
Date: Fri, 5 Oct 2007 00:14:14 -0700 [thread overview]
Message-ID: <449c8cfc0710050014j9bbf057ka108ee27dea49a89@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
Hello,
(My apologies if my incorrectly addressed subscribe message went to the list)
I noticed that my mutt wasn't correctly detecting the signature block
on the end of the automated emails I was receiving from the script in
contrib. I've made this trivial change in my local copy of the script,
but I figured that if I was going to be modifying the source code I
should share my changes.
--
Eric Mertens
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Correct-signature-block-delimiter-in-post-receive-em.patch --]
[-- Type: text/x-patch; name="0001-Correct-signature-block-delimiter-in-post-receive-em.patch", Size: 792 bytes --]
From 119f84fa6f6bb33c6fc524ab4277d38bebc10468 Mon Sep 17 00:00:00 2001
From: Eric Mertens <emertens@gmail.com>
Date: Fri, 5 Oct 2007 00:06:52 -0700
Subject: [PATCH] Correct signature block delimiter in post-receive-email by adding a trailing space
This change allows mail clients like Mutt to easily detect the signature
and is consistent with the signature block article on Wikipedia.
---
contrib/hooks/post-receive-email | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index cbbd02f..828651a 100644
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -198,7 +198,7 @@ generate_email_footer()
hooks/post-receive
- --
+ --
$projectdesc
EOF
}
--
1.5.3.4
next reply other threads:[~2007-10-05 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 7:14 Eric Mertens [this message]
2007-10-05 8:13 ` Correction for post-receive-email Andy Parkins
2007-10-05 8:54 ` Andreas Ericsson
2007-10-05 12:35 ` Bill Lear
2007-10-05 14:29 ` Andy Parkins
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=449c8cfc0710050014j9bbf057ka108ee27dea49a89@mail.gmail.com \
--to=emertens@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).