From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@gnus.org
Subject: Re: Fixing In-Reply-To problems
Date: 07 Jan 1998 13:03:52 -0800 [thread overview]
Message-ID: <x7pvm4nghz.fsf@des.castles.com> (raw)
In-Reply-To: Paul Franklin's message of "07 Jan 1998 12:02:59 -0800"
>>>>> On 07 Jan 1998 12:02:59 -0800, Paul Franklin <paul@cs.washington.edu> said:
Paul> I know, it's just a hack to replace the existing hack, but I
Paul> think it'll work more often, because I've observed that a
Paul> message's ID is usually longer than its sender's email address.
Well, that is better than the current function most likely. You're
probably right, they would almost always be longer, but certainly not
all the time... I'd guess more right than not, however, which isn't
true of the current function which I'd guess is getting about 50% of
the cases (mailer's choice on which to put first on the line).
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-01-07 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-07 18:48 Wes Hardaker
1998-01-07 20:02 ` Paul Franklin
1998-01-07 21:03 ` Wes Hardaker [this message]
1998-01-12 22:31 ` Lars Magne Ingebrigtsen
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=x7pvm4nghz.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
--cc=ding@gnus.org \
/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).