From: Steinar Bang <sb@metis.no>
Subject: Re: making gnus-summary-reparent-thread work right with nnml
Date: 24 Nov 1997 14:53:52 +0100 [thread overview]
Message-ID: <whbtza5rf3.fsf@norne.troll.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "23 Nov 1997 07:08:00 +0100"
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Steinar Bang <sb@metis.no> writes:
>> If the article already has a References header, the new article number
>> is inserted at the start (looking at the code at the end of this
>> message), and I belive it should be inserted at the end...? (at least
>> that's the way I understand 2.2.5 of RFC 1036...)
> Yup. Fix in Quassia Gnus v0.14.
I haven't tried using reparenting on articles with an existing, bogus
References header (eg. Eudora Pro 3.x), but I've noted that qgnus 0.14
immediately correctly rethreads articles without a previous references
header.
But! There's still no References header when you toggle on all headers
after reparenting. And "Fetch parent of article" still reports no
"References in article...".
I see now, when I enter that group from gnus 5.5.67, that the article
reparented in qgnus now has a References header. Maybe exiting and
entering the group fixed it? Hmm... still not silk-smooth, tho'...
- Steinar
prev parent reply other threads:[~1997-11-24 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-18 16:13 Steinar Bang
1997-11-19 9:14 ` Steinar Bang
1997-10-24 21:01 ` automagicly compressed nnml files St. Suika Roberts
1997-10-24 23:39 ` Lars Magne Ingebrigtsen
1997-10-26 15:39 ` Simon Josefsson
1997-10-27 11:22 ` Simon Josefsson
1997-10-29 5:09 ` David Hedbor
1997-11-05 12:50 ` Lars Magne Ingebrigtsen
1997-11-06 23:37 ` David Hedbor
1997-11-13 21:14 ` Lars Magne Ingebrigtsen
1997-11-18 23:14 ` David Hedbor
1997-11-23 6:08 ` Lars Magne Ingebrigtsen
1997-11-23 6:08 ` making gnus-summary-reparent-thread work right with nnml Lars Magne Ingebrigtsen
1997-11-24 13:53 ` Steinar Bang [this message]
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=whbtza5rf3.fsf@norne.troll.no \
--to=sb@metis.no \
/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).