From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Fixing In-Reply-To problems
Date: 07 Jan 1998 10:48:26 -0800 [thread overview]
Message-ID: <x77m8cqfwl.fsf@des.castles.com> (raw)
So, I've been getting sick of broken threads due to broken mailers
sending different types of In-Reply-To headers. I've been
thinking... Couldn't something be done like:
1 Find In-Reply-To header
2 Search for <blah> on the line
3 Check to see if blah is a valid existing reference
- Yes: use it
- No: go back to 2 and continue search.
4 none matched, bail as normal and collect into dummy, or whatever the
default is set to.
Right now, it is just taking a predefined location for the reference
header, which frequently is wrong due to email addresses, etc,
confusing it. Can't we compare against known existing message ids
before using it? Just a thought...
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next reply other threads:[~1998-01-07 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-07 18:48 Wes Hardaker [this message]
1998-01-07 20:02 ` Paul Franklin
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=x77m8cqfwl.fsf@des.castles.com \
--to=wjhardaker@ucdavis.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).