From: Lee Willis <lee@gbdirect.co.uk>
Subject: [OT] broken-reply-to
Date: 09 Nov 1999 15:16:57 +0000 [thread overview]
Message-ID: <lz4sevy9sm.fsf@landlord.gbdirect.co.uk> (raw)
Can anyone provide me with a pointer to the discussion of why
mailing-lists shouldn't put in Reply-To headers.
Cheers
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next reply other threads:[~1999-11-09 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 15:16 Lee Willis [this message]
1999-11-09 16:02 ` Hrvoje Niksic
1999-11-09 16:27 ` Toby Speight
1999-11-09 16:35 ` Lee Willis
1999-11-09 16:53 ` Toby Speight
1999-11-09 20:01 ` Karl EICHWALDER
1999-11-11 13:31 ` Lars Magne Ingebrigtsen
1999-11-11 15:59 ` Toby Speight
1999-11-11 22:41 ` Karl EICHWALDER
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=lz4sevy9sm.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).