From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: cc:Mail messed up Re[2]: subjects
Date: 28 Mar 1997 14:50:53 -0500 [thread overview]
Message-ID: <vxk9137iyn6.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Joe Hildebrand's message of 28 Mar 1997 12:28:27 -0600
Joe Hildebrand <hildjj@mindspring.com> writes:
> I have some people with whom I associate that use cc:Mail. It tends
> to munge Subject lines differently than normal. When you reply to a
> reply, it adds Re[2]: to the subject, taking out the Re:.
> Can message.el be changed so that whenever it is stripping out Re:'s,
I would say that this falls under the same problem as German versions
of certain Microsoft products using "FW:" instead of "Re:", where the
proper fix is to prevail upon the authors of the broken software to
repair it for their next release, rather than asking the rest of the
universe to accommodate the bugs.
next prev parent reply other threads:[~1997-03-28 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-28 18:28 Joe Hildebrand
1997-03-28 19:50 ` Karl Kleinpaste [this message]
1997-03-28 20:39 ` Dewey M. Sasser
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=vxk9137iyn6.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).