From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] add a reply-to hook, for setting the Reply To field.
Date: Sat, 26 Apr 2008 23:50:05 -0700 [thread overview]
Message-ID: <1209278999-sup-9027@south> (raw)
Reformatted excerpts from William Morgan's message of 2008-04-26:
> Maybe add the list of allowable return values.
Heck, you could generate this automatically. Self-documenting code,
literally!
--
William <wmorgan-sup at masanjin.net>
next reply other threads:[~2008-04-27 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 6:50 William Morgan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-27 6:49 William Morgan
2008-04-05 5:48 [sup-talk] Setting reply to -- hook or config? Jeff Balogh
2008-04-24 5:23 ` [sup-talk] [PATCH] add a reply-to hook, for setting the Reply To field Jeff Balogh
2008-04-24 5:56 ` Marc Hartstein
2008-04-24 14:38 ` Jeff Balogh
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=1209278999-sup-9027@south \
--to=wmorgan-sup@masanjin.net \
/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