From: Harry Putnam <reader@newsguy.com>
Subject: Re: No Cc on wide reply
Date: 22 Jul 2000 06:43:56 -0700 [thread overview]
Message-ID: <m2n1jap9er.fsf@reader.ptw.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 22 Jul 2000 14:03:55 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Does the message have a Mail-Copies-To header?
Erp.. yup thats it. Now what is the appropriate thing in this case.
The message containing the Cc was Cced to me but the author has
included:
Mail-Copies-To: never
So apparently the author himself freely Cc's but asks not to be Cc'ed
himself. Hmmm ...
next prev parent reply other threads:[~2000-07-22 13:43 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 [this message]
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
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=m2n1jap9er.fsf@reader.ptw.com \
--to=reader@newsguy.com \
/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).