Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: No Cc on wide reply
Date: Sun, 30 Jul 2000 10:30:47 -0400	[thread overview]
Message-ID: <m3bszfvgfc.fsf@peorth.rgo.gweep.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 29 Jul 2000 18:16:19 +0200"

* Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)  on Sat, 29 Jul 2000
| In particular, `remove jrl@frob.org from list of recipients' (the
| operation intended by `Mail-Copies-To: never') is not the same as
| `set list of recipients to list@blarfl.org'.

Hmmm... okay, I can see that.

| Apparently, MCT offers functionality not present with the Reply-To
| header, even for mail.  Should the (proposed) standard for MCT be
| changed?

No.  Given that handling of mail and news is different, the semantics of
the header would change a little based on the backend.  That is confusing.

Besides, duplicate suppression already covers the issue, I think.
-- 
Rat <ratinox@peorth.gweep.net>    \ Ingredients of Happy Fun Ball include an
Minion of Nathan - Nathan says Hi! \ unknown glowing substance which fell to
PGP Key: at a key server near you!  \ Earth, presumably from outer space.



  parent reply	other threads:[~2000-07-30 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-22  4:11 Harry Putnam
2000-07-22 12:03 ` Kai Großjohann
2000-07-22 13:43   ` Harry Putnam
2000-07-22 14:02     ` Stainless Steel Rat
2000-07-23  9:43       ` Kai Großjohann
2000-07-23 15:17         ` Stainless Steel Rat
2000-07-24  9:22           ` Simon Josefsson
2000-07-24 16:46             ` Stainless Steel Rat
     [not found]               ` <vaf7la4ud2k.fsf@lucy.cs.uni-dortmund.de>
2000-07-30 14:30                 ` Stainless Steel Rat [this message]
2000-07-24 15:05           ` Paul Jarc
2000-07-24 16:47             ` Stainless Steel Rat
2000-07-25  6:55           ` Kai Großjohann

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=m3bszfvgfc.fsf@peorth.rgo.gweep.net \
    --to=ratinox@peorth.gweep.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;
as well as URLs for NNTP newsgroup(s).