From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kuba@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS3215 2.6.0.0/16
X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,
	SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.2
Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 858DF1F953
	for <meta@public-inbox.org>; Fri,  7 Jan 2022 02:22:44 +0000 (UTC)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dfw.source.kernel.org (Postfix) with ESMTPS id 7B19261EB8;
	Fri,  7 Jan 2022 02:22:43 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id CAC2AC36AEB;
	Fri,  7 Jan 2022 02:22:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=k20201202; t=1641522162;
	bh=1N+r4bAyzbwA+wfUtKOm7xkhZH9qnoqTCF1jB627nrw=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
	b=ugRMjsPjGsny8bukc35ZEq8ia6FtzkldA6tUuv/hm7LuUwHmMWHs2tgnSR3bPjI7E
	 KgOlUWFyd7bamINJbK3bvEgbwmCjEGbJavkbitKkEDHhIl1bNTTPwVw5zrfuz1nA6F
	 Bd7RRxtxJec0LQ64XaAIAU4vkX0rS81QDgSxLevmi3kp0RSyYhz23xTNec4lIhYtVZ
	 WZjOI5ZpffHCpyeC179os9fEO8pA5/sHuRqoKbBmtupWpMRLHExFsU2dLCU7k0jOOd
	 dxZeBGZ/qkT+4frrz6jJUywi6Gir9Ub9GuKyNthntyaSeG4RJkZQExQEZW5D49DvSg
	 TUI1AAsNxBIVA==
Date: Thu, 6 Jan 2022 18:22:41 -0800
From: Jakub Kicinski <kuba@kernel.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: MH & thread support
Message-ID: <20220106182241.246818c4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
In-Reply-To: <877dbc5nnq.fsf@kyleam.com>
References: <20220106101020.09638bd8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
	<877dbc5nnq.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: <meta.public-inbox.org>

On Thu, 06 Jan 2022 20:40:09 -0500 Kyle Meyer wrote:
> >  - is there a way to get lei to fetch a particular thread? It seems
> >    like using a bare msg-id as the search term mostly works, but it 
> >    also fetches in any threads which were referring to the thread of
> >    interest by posting a link  
> 
> You can search with the "mid:" prefix and then pull in the entire thread
> with -t/--threads:
> 
>   $ lei q -f ldjson \
>     mid:20211119204916.grergcuzj5gcic6c@meerkat.local | \
>     jq '[.blob,.s,.f[0][0]]'
>   [
>     "7e49832370e95afb54298d21ea4c10d338bb3a7b",
>     "RFC: should lei inject its own \"Received:\" header?",
>     "Konstantin Ryabitsev"
>   ]
> 
> 
>   $ lei q -t -f ldjson \
>     mid:20211119204916.grergcuzj5gcic6c@meerkat.local | \
>     jq '[.blob,.s,.f[0][0]]'
>   [
>     "7e49832370e95afb54298d21ea4c10d338bb3a7b",
>     "RFC: should lei inject its own \"Received:\" header?",
>     "Konstantin Ryabitsev"
>   ]
>   [
>     "70c49f363594e94d89a14bcb57c45d45cac49172",
>     "Re: RFC: should lei inject its own \"Received:\" header?",
>     "Eric Wong"
>   ]

Perfect, thanks!