unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Alison Schofield <alison.schofield@intel.com>
Cc: meta@public-inbox.org, Dave Hansen <dave.hansen@intel.com>
Subject: Re: Threaded responses to queries (x86)
Date: Wed, 31 May 2023 07:50:53 +0000	[thread overview]
Message-ID: <20230531075053.M93596@dcvr> (raw)
In-Reply-To: <ZG+vV5X5bSm2pQjk@aschofie-mobl2>

Alison Schofield <alison.schofield@intel.com> wrote:
> Hi,
> 
> I use Lore and find the threaded results of many Lore Lists useful.
> Then there is x86. It doesn't have a list, so I query:
> 
> https://lore.kernel.org/all/?q=tc:x86@kernel.org
> 
> The result of that query is not threaded. Can I change my query to
> get the threading, or, as Dave Hansen suggested below, does the
> underlying code need to change.  

You can use the `&x=t' parameter to give something similar to
the /$MSGID/T/ URLs which is the "flat" thread output:

	https://lore.kernel.org/all/?q=tc:x86@kernel.org&x=t

The `#t' anchor brings you directly to the thread skeleton overview:

	https://lore.kernel.org/all/?q=tc:x86@kernel.org&x=t#t

There's also an undocumented t=1 parameter which collapses
threads(*) and might reduce clutter from busy threads:

	https://lore.kernel.org/all/?q=tc:x86@kernel.org&x=t&t=1#t

(*) t=1 was only intended for the mbox downloads, but ends up
    affecting HTML output

> Dave's diff follows. I don't have a means of trying that out.

Having a dothread= parameter seems redundant with x=t; but
I agree x=t can display too much and the default summary
view not enough...

> I appreciate help in improving the view of x86!

It's tricky to get the because search results can be ordered by
either relevance or date.  And also the relevance percentage
next to each message.

I wonder if lore can expose x86@kernel.org as its own inbox even
if it's technically not a subscribable mailing list.  That would
be much faster (but less space-efficient) than issuing a Xapian
query to get x86@kernel.org mails.

  reply	other threads:[~2023-05-31  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 18:56 Threaded responses to queries (x86) Alison Schofield
2023-05-31  7:50 ` Eric Wong [this message]
2023-05-31 12:05   ` Konstantin Ryabitsev

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230531075053.M93596@dcvr \
    --to=e@80x24.org \
    --cc=alison.schofield@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=meta@public-inbox.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).