From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-message-archive-method is confusing
Date: Mon, 23 Jul 2001 23:04:53 -0700 [thread overview]
Message-ID: <2ng0bmlv5m.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <vafofqennmz.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 21 Jul 2001 20:27:32 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On Fri, 20 Jul 2001, Paul Jarc wrote:
>
>> How does gnus-outgoing-message-group relate to all this? Is it
>> obsoleted by g-m-a-g? Or used for something slightly different?
>
> If I remember correctly, I had an exchange like this with Lars:
>
> Me: So, what's the difference between gnus-outgoing-message-group and
> gnus-message-archive-group?
>
> Lars: The former is older.
>
> Me: So, is gnus-outgoing-message-group going to go away?
>
> Lars: No.
>
> I'm not sure what to make of this... IMVHO the two ways are not
> needed. But on the other hand it seems that using
> gnus-message-archive-group means that the Gcc header is not inserted
> in all cases. Hm. Ah, yes, maybe it has to do with the gcc-self
> group parameter. Yeah, I think with gnus-outgoing-message-group and
> the gcc-self parameter you get two Gcc headers, but with
> gnus-message-archive-group and the gcc-self parameter you get only one
> (the gcc-self one).
>
> Can anyone confirm this?
By reading the code, I think you are right.
ShengHuo
prev parent reply other threads:[~2001-07-24 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 8:39 Kai Großjohann
2001-07-20 19:33 ` Paul Jarc
2001-07-21 18:27 ` Kai Großjohann
2001-07-24 6:04 ` ShengHuo ZHU [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=2ng0bmlv5m.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.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).