From: Jarmo Hurri <jarmo.hurrigarbage@cs.helsinki.fi>
Subject: Re: orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number
Date: Mon, 15 Jan 2007 10:15:02 +0200 [thread overview]
Message-ID: <yup4ac0kr9ix.fsf@sbz-32.cs.helsinki.fi> (raw)
In-Reply-To: <mailman.3033.1168717393.2155.info-gnus-english@gnu.org>
Reiner> Again, 439307 is part of a loose thread.
Yes, good point.
Reiner> I don't know how orphaned articles / loose threads are
Reiner> supposed to be handled with
Reiner> `gnus-thread-sort-by-most-recent-number'. Anyone? (Maybe we
Reiner> should just document the current behavior if we can't handle
Reiner> orphans better?)
Isn't it still weird that it works as expected without the 'not'
reversing specification? I mean, in that case even orphans seem to be
handled pretty much perfectly. Or?
BTW, with the idea that this might be related to orphans, can you now
reproduce the problem on your system, or should I still strive to see
what happens with minimal configuration? (I mean, this could still all
just be something about my configuration.)
--
Jarmo Hurri
Commercial email countermeasures included in header email
address. Remove all garbage from header email address when replying,
or just use firstname.lastname@cs.helsinki.fi .
prev parent reply other threads:[~2007-01-15 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 17:49 Simple thread sorting question Jarmo Hurri
2007-01-11 21:06 ` Reiner Steib
2007-01-12 7:10 ` Jarmo Hurri
2007-01-12 10:43 ` Reiner Steib
2007-01-12 14:17 ` Jarmo Hurri
2007-01-12 17:05 ` Reiner Steib
2007-01-13 10:37 ` Jarmo Hurri
2007-01-13 12:13 ` orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number (was: Simple thread sorting question) Reiner Steib
[not found] ` <mailman.3033.1168717393.2155.info-gnus-english@gnu.org>
2007-01-15 8:15 ` Jarmo Hurri [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=yup4ac0kr9ix.fsf@sbz-32.cs.helsinki.fi \
--to=jarmo.hurrigarbage@cs.helsinki.fi \
/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).