all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Welsh Duggan <mwd@cert.org>
Cc: 21462@debbugs.gnu.org
Subject: bug#21462: 25.0.50; Gnus thread gathering and sorting inverted
Date: Tue, 09 Feb 2016 11:50:54 +1100	[thread overview]
Message-ID: <87lh6uiu4x.fsf@gnus.org> (raw)
In-Reply-To: <tntd1s7f7tu.fsf@watermonitor.yellow.cert.org> (Michael Welsh Duggan's message of "Mon, 08 Feb 2016 12:08:45 -0500")

Michael Welsh Duggan <mwd@cert.org> writes:

>>> 1) gnus-make-threads -> gathers articles into threads by ref
>>> 2) gnus-cut-threads  -> removes "uninteresting" articles from the
>>>    threads
>>> 3) gnus-sort-threads -> sorts the threads (with respect to each other thread)
>>> 4) gnus-summary-thread-gathering-function -> gathers threads with
>>>    similar characteristics (subject, reference) into a single thread
>>> 5) gnus-sort-gathered-threads -> sorts the articles within each thread

[...]

> Is there a good reason for step 3 and 4 above to be in the given order
> instead of the reverse?

I think the reason they are in that order is for historical (and
backwards compatible) reasons: The predicates that work on thread
sorting will normally fail on gathered threads (which are lists of
thread roots).  I think.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2016-02-09  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 17:34 bug#21462: 25.0.50; Gnus thread gathering and sorting inverted Michael Welsh Duggan
2016-02-07  5:53 ` Lars Ingebrigtsen
2016-02-07  7:40   ` Michael Welsh Duggan
2016-02-08  4:51     ` Lars Ingebrigtsen
2016-02-08 17:08       ` Michael Welsh Duggan
2016-02-09  0:50         ` Lars Ingebrigtsen [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=87lh6uiu4x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=21462@debbugs.gnu.org \
    --cc=mwd@cert.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.