Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: message-subject-re
Date: Thu, 30 Aug 2001 09:52:19 +1000	[thread overview]
Message-ID: <877kvm4e6k.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <g08bskyeid6.fsf@zzz.cisco.com> (Michael.Cook@cisco.com's message of "Wed, 29 Aug 2001 16:11:49 -0400")

On Wed, 29 Aug 2001, Michael Cook wrote:
> Frank Schmitt <Azzrael@rz-online.de> writes:
> 
>> Henrik Enberg <henrik@enberg.org> writes:
>>
>>>Ick, does this mean that we're going to see people posting with Gnus
>>>using Sv: style subject lines and non-standard sig separators?
>>>
>>>I think some stuff _should_ be hardcoded.
>>
>> 100% acknowledge.
> 
> well, all i really wanted to do was suppress the "Re:".
> that seems reasonable, no?

It's certainly not in the category of "best practice" and, while I can't
find an RFC reference that mandates it for email, it's strongly
suggested by RFC822...

...and it does mean that it's not going to be possible for some email
clients that use the subject line to sort threads to tell that your
messages are part of one.

Er, /why/ do you want to do that?
        Daniel

-- 
If Americans can be divorced for "incompatibility of temper" I cannot conceive
why they are not all divorced. I have known many happy marriages, but never a
compatible one.
        -- _What is Wrong with the World_ (1910)


  reply	other threads:[~2001-08-29 23:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29 18:25 message-subject-re Michael.Cook
2001-08-29 18:29 ` message-subject-re Paul Jarc
2001-08-29 18:34   ` message-subject-re Michael.Cook
2001-08-29 18:48     ` message-subject-re Paul Jarc
2001-08-29 19:33       ` message-subject-re Simon Josefsson
2001-08-29 19:40         ` message-subject-re Henrik Enberg
2001-08-29 19:46           ` message-subject-re Paul Jarc
2001-08-29 20:08             ` message-subject-re Michael.Cook
2001-08-29 19:51           ` message-subject-re Frank Schmitt
2001-08-29 20:11             ` message-subject-re Michael.Cook
2001-08-29 23:52               ` Daniel Pittman [this message]
2001-08-30  1:50                 ` message-subject-re Michael.Cook
2001-08-30  2:31                   ` message-subject-re Daniel Pittman
2001-08-30  4:44                   ` message-subject-re Paul Jarc
2001-08-30 16:32                     ` message-subject-re Michael.Cook
2001-08-30 16:39                       ` message-subject-re Jesper Harder
2001-08-30 13:38             ` message-subject-re Per Abrahamsen
2001-08-29 19:43         ` message-subject-re Paul Jarc
2001-08-29 19:51         ` message-subject-re Simon Josefsson
2001-08-30 14:17           ` message-subject-re Per Abrahamsen
2001-08-31 23:26             ` message-subject-re Simon Josefsson
2001-09-01 14:34               ` message-subject-re Per Abrahamsen
2001-08-30  2:16   ` message-subject-re Steve Youngs
2001-09-05 15:02   ` message-change-subject-interactively (was: message-subject-re) Toby Speight
2001-09-05 15:12   ` message-subject-re Colin Marquardt
2001-09-05 16:10     ` message-subject-re Michael.Cook

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=877kvm4e6k.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    /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).