From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: Lore link problems with lossy lists
Date: Thu, 1 Apr 2021 17:25:53 -0400 [thread overview]
Message-ID: <20210401212553.wsaqzxfwf45tf7cx@chatter.i7.local> (raw)
In-Reply-To: <13b77ad8f00b5590baca6203cc7b073df477e993.camel@HansenPartnership.com>
On Thu, Apr 01, 2021 at 10:07:34AM -0700, James Bottomley wrote:
> Put more broadly: when pulling up a thread by messageid, could we get a
> redirect always to the entire set of replies lore has even if they
> traverse multiple lists ... forget the lossy list problem, annoying
> people drop and add various lists from CC's all the time, but in spite
> of this I would like to be able to see the full thread.
Soon (TM).
https://lore.kernel.org/workflows/20201201184814.GA32272@dcvr/
I expect this feature will be in place within the next few months, and not
just in b4 but for all lore lookups.
-K
prev parent reply other threads:[~2021-04-01 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 17:07 Lore link problems with lossy lists James Bottomley
2021-04-01 21:25 ` Konstantin Ryabitsev [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=20210401212553.wsaqzxfwf45tf7cx@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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 NNTP newsgroup(s).