From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: Fixing In-Reply-To problems
Date: 07 Jan 1998 12:02:59 -0800 [thread overview]
Message-ID: <r9qra6kyrv0.fsf@hirame.cs.washington.edu> (raw)
In-Reply-To: Wes Hardaker's message of "07 Jan 1998 10:48:26 -0800"
I'll suggest a hack-ish alternative...
Use the longest string which looks like a message ID.
I know, it's just a hack to replace the existing hack, but I think
it'll work more often, because I've observed that a message's ID is
usually longer than its sender's email address.
--Paul
next prev parent reply other threads:[~1998-01-07 20:02 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 [this message]
1998-01-07 21:03 ` Wes Hardaker
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=r9qra6kyrv0.fsf@hirame.cs.washington.edu \
--to=paul@cs.washington.edu \
/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).