From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: [PATCH] Re: Does Mail-Followup-To generation work?
Date: Fri, 01 Mar 2002 16:29:47 -0500 [thread overview]
Message-ID: <m3lmdcrn6m.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vaf4rk0rniv.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 01 Mar 2002 22:22:48 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> But on the other hand, why not change the MFT code to always look at
> the group parameters?
Because it's in message.el and thus shouldn't depend on Gnus group
parameters, I guess. But it could look at the group parameters only
if available, as well as the variables it uses now. Would that
violate any encapsulation principle here?
paul
next prev parent reply other threads:[~2002-03-01 21:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 15:26 Does Mail-Followup-To generation? Nevin Kapur
2002-03-01 15:42 ` Does Mail-Followup-To generation work? Nevin Kapur
2002-03-01 15:42 ` Nevin Kapur
2002-03-01 15:52 ` Does Mail-Followup-To generation? Kai Großjohann
2002-03-01 15:52 ` Kai Großjohann
2002-03-01 16:18 ` Nevin Kapur
2002-03-01 16:18 ` Nevin Kapur
2002-03-01 16:20 ` Paul Jarc
2002-03-01 16:20 ` Paul Jarc
2002-03-01 16:53 ` [PATCH] Re: Does Mail-Followup-To generation work? Nevin Kapur
2002-03-01 16:53 ` Nevin Kapur
2002-03-01 17:04 ` Josh Huber
2002-03-01 17:04 ` Josh Huber
2002-03-01 17:34 ` Nevin Kapur
2002-03-01 17:34 ` Nevin Kapur
2002-03-01 20:43 ` Kai Großjohann
2002-03-01 20:43 ` Kai Großjohann
2002-03-01 20:54 ` Paul Jarc
2002-03-01 20:54 ` Paul Jarc
2002-03-01 21:22 ` Kai Großjohann
2002-03-01 21:22 ` Kai Großjohann
2002-03-01 21:29 ` Paul Jarc [this message]
2002-03-02 21:22 ` Kai Großjohann
2002-03-02 21:22 ` Kai Großjohann
2002-03-01 21:29 ` Paul Jarc
2002-03-01 17:21 ` Does Mail-Followup-To generation? Kai Großjohann
2002-03-01 17:21 ` Kai Großjohann
2002-03-01 18:10 ` Christoph Conrad
2002-03-01 18:10 ` Christoph Conrad
2003-01-02 2:07 ` Lars Magne Ingebrigtsen
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=m3lmdcrn6m.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).