Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] [PATCH] Configurable automatic CC and BCC
Date: Fri, 2 Nov 2007 12:21:30 +0100	[thread overview]
Message-ID: <6205b42d0711020421y6198e446s77bdab118666e20c@mail.gmail.com> (raw)
In-Reply-To: <1193975643-sup-9164@south>

Hi William and all :)

I'll have a look into Marcus patch and see if I can use it to make the same
functionality. Thanks for the idea !

-- 
Pierre.

On 11/2/07, William Morgan <wmorgan-sup at masanjin.net> wrote:
>
> 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>
> _______________________________________________
> sup-talk mailing list
> sup-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>



-- 
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071102/1b88c3c7/attachment.html 


      reply	other threads:[~2007-11-02 11:21 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
2007-11-02 11:21     ` Pierre Baillet [this message]

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=6205b42d0711020421y6198e446s77bdab118666e20c@mail.gmail.com \
    --to=pierre@baillet.name \
    /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