From: Colin Rafferty <craffert@ml.com>
Subject: Re: [++] Re: Deleting a message draft
Date: 13 Feb 1998 11:34:10 -0500 [thread overview]
Message-ID: <ocr4t23tqf1.fsf@ml.com> (raw)
In-Reply-To: Lars Balker Rasmussen's message of "13 Feb 1998 11:54:08 +0100"
Lars Balker Rasmussen writes:
> Colin Rafferty <craffert@ml.com> writes:
>> ois Pinard writes:
> I hate supercite.
You're in a bad mood today.
>> This posting adheres to the SELF-DISCIPLINE guidelines for better
>> USENET discussions. See http://www.eiffel.com/discipline.
> I hate the SELF-DISCIPLINE guidelines (it breaks the flow of summary
> buffers, so you can't see what articles have been replied to...)
(setq gnus-thread-ignore-subject t)
--
Colin
next prev parent reply other threads:[~1998-02-13 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-12 20:56 François Pinard
1998-02-12 22:30 ` [++] " Colin Rafferty
1998-02-13 10:54 ` Lars Balker Rasmussen
1998-02-13 14:08 ` Jake Colman
1998-02-13 16:34 ` Colin Rafferty [this message]
1998-02-13 22:12 ` Lars Balker Rasmussen
1998-02-15 0:10 ` Aaron M. Ucko
1998-02-13 10:48 ` Lars Balker Rasmussen
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=ocr4t23tqf1.fsf@ml.com \
--to=craffert@ml.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).