From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Configurable automatic CC and BCC
Date: Thu, 01 Nov 2007 20:54:43 -0700 [thread overview]
Message-ID: <1193975643-sup-9164@south> (raw)
In-Reply-To: <6205b42d0710310142r4c1a699co6776e3180a21e46c@mail.gmail.com>
Hi Pierre,
Sorry for taking so long to review this. Other patch submitters, don't
worry---I'm going through them one by one and nothing will be ignored!
Excerpts from Pierre Baillet's message of Wed Oct 31 01:42:58 -0700 2007:
> maybe you came accross my patch, but I don't know what you think about
> integrating it to the trunk or not. Maybe it's not near enough in your
> TODO, too :)
I like this functionality. But, instead of another set of configuration
options, I would rather see a before-edit hook, which would allow for
auto-filling cc/bcc programmatically and for all sorts of other fun
stuff. Would you be interested in submitting a patch for that instead?
Marcus just submitted a before-add hook which you can probably use as a
reference.
What do you think?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-11-02 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 12:17 Pierre Baillet
2007-10-31 8:42 ` Pierre Baillet
2007-11-02 3:54 ` William Morgan [this message]
2007-11-02 11:21 ` Pierre Baillet
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=1193975643-sup-9164@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