From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: gnus-split-references tweak
Date: Wed, 06 Feb 2002 15:50:24 -0500 [thread overview]
Message-ID: <m3vgdal4gp.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3n0ym4eyt.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 06 Feb 2002 13:55:32 -0500")
I wrote:
> I've found Message-IDs generated by Lotus Notes that contain a space
> just before the ">". (Yep, they're malformed.) Gnus dutifully
> preserves them in its References, but then it's unable to recognize
> them for threading. This patch maks them recognizable: everything
> from one "<" to the next "<" is included in a reference except
> trailing whitespace.
Hm. It seems this actually isn't sufficient for recognizing them
anyway. I'm not sure what else would need to be changed, though.
paul
next prev parent reply other threads:[~2002-02-06 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 18:55 Paul Jarc
2002-02-06 20:50 ` Paul Jarc [this message]
2002-02-06 20:50 ` Jesper Harder
2002-02-06 21:32 ` Paul Jarc
2002-02-07 1:59 ` Jesper Harder
2002-02-07 16:30 ` Paul Jarc
2002-02-07 20:06 ` Paul Jarc
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=m3vgdal4gp.fsf@multivac.cwru.edu \
--to=prj@po.cwru.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).