From: col@baibell.org (Colin Bell)
Subject: [sup-talk] [PATCH] New hook to allow formatting of message headers
Date: Wed, 21 Nov 2007 15:26:40 +1100 [thread overview]
Message-ID: <1195618839-sup-4347@lankhmar> (raw)
Hi,
This patch allows you to format the headers shown in the Detailed
Headers view. Also attached is an example hook which will show the
email client and a spam header.
--
Col
-------------- next part --------------
A non-text attachment was scrubbed...
Name: headers.diff
Type: application/octet-stream
Size: 1193 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071121/a752531a/attachment.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: format-message-headers.rb
Type: application/octet-stream
Size: 202 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071121/a752531a/attachment-0001.obj
next reply other threads:[~2007-11-21 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 4:26 Colin Bell [this message]
2007-12-05 18:12 ` William Morgan
2007-12-05 18:36 ` William Morgan
2007-12-06 17:12 ` Nicolas Pouillard
2007-12-06 17:14 ` Nicolas Pouillard
2007-12-07 18:10 ` William Morgan
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=1195618839-sup-4347@lankhmar \
--to=col@baibell.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