From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: mail-{followup,copies}-to on this list
Date: 14 Feb 2001 16:51:20 -0500 [thread overview]
Message-ID: <m38zn9djbl.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: NAGY Andras's message of "14 Feb 2001 21:44:26 +0100"
NAGY Andras <nagya@inf.elte.hu> writes:
> Please correct me if I interpret this wrong, or stop sending me
> personal followups.
I discourage duplicates by setting Mail-Followup-To, and bouncing any
duplicates that get sent anyway. I'm subscribed to ding as
prj-ding@...; if anything comes to prj@... with ding@gnus.org in To:
or Cc:, that copy gets bounced.
paul
next prev parent reply other threads:[~2001-02-14 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 20:44 NAGY Andras
2001-02-14 21:36 ` ShengHuo ZHU
2001-02-14 21:51 ` Paul Jarc [this message]
2001-02-14 22:05 ` Kai Großjohann
2001-02-14 22:48 ` NAGY Andras
2001-02-15 13:14 ` Per Abrahamsen
2001-02-15 13:56 ` NAGY Andras
2001-02-15 14:13 ` Per Abrahamsen
2001-02-15 18:37 ` Jake Colman
2001-02-15 19:03 ` Per Abrahamsen
2001-02-15 13:53 ` David S. Goldberg
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=m38zn9djbl.fsf@multivac.student.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).