From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: mail-{followup,copies}-to on this list
Date: 15 Feb 2001 14:56:23 +0100 [thread overview]
Message-ID: <dzcpugkqcc8.fsf@pandora.inf.elte.hu> (raw)
In-Reply-To: <rjk86sozov.fsf@ssv2.dina.kvl.dk>
Okay, you convinced me. I've chosen the mail-copies-to header.
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 4. He can try flaming on the list, and hope the receivers will make it
> their problem. I strongly discourage selecting this option.
Sorry for this.
Andras
next prev parent reply other threads:[~2001-02-15 13:56 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
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 [this message]
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=dzcpugkqcc8.fsf@pandora.inf.elte.hu \
--to=nagya@inf.elte.hu \
/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).