From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Red Gnus: Posted & e-mailed detection
Date: 19 Mar 1996 21:55:38 +0100 [thread overview]
Message-ID: <x64trkg9s1.fsf@eyesore.no> (raw)
In-Reply-To: Russ Allbery's message of Tue, 19 Mar 1996 07:30:29 -0800 (PST)
Russ Allbery <eagle@cyclone.Stanford.EDU> writes:
> It could also just be a new function, so people would have to explicitly
> check. That would probably be the best way of doing it.
That might be useful, so I've added it to the todo list. Automatic
checking of all mail messages sounds like overkill, though.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-03-19 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-19 15:30 Russ Allbery
1996-03-19 20:55 ` Lars Magne Ingebrigtsen [this message]
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=x64trkg9s1.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).