From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=1.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_BL_SPAMCOP_NET, RCVD_IN_DNSWL_NONE,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from mail-vs1-xe43.google.com (mail-vs1-xe43.google.com [IPv6:2607:f8b0:4864:20::e43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1AE311F619 for ; Thu, 19 Mar 2020 18:46:00 +0000 (UTC) Received: by mail-vs1-xe43.google.com with SMTP id i25so2356227vsq.9 for ; Thu, 19 Mar 2020 11:46:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=mgNZ3SwGvtKC3EKGy9RfkvoE4iWaxhQnsbEpbqk959E=; b=BqT9owByFSHZR1fL/EkvTmif+kOa/wOoADUrm3hNp8K1X6hpcIioRfAbyjqHIlEEGq 4Y3svi8ATobU0ybZ0EP6/aaJkvdDKSQcTnIs0NMHaR1ixinjFM6B1M4QDDmV+x6bnaKy k1OwH7S1ClG5qdI4zI7dHn6/p4oKC7l/pxdfg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=mgNZ3SwGvtKC3EKGy9RfkvoE4iWaxhQnsbEpbqk959E=; b=TYOKZ4v2F0pFa2zYX3EBxR9Mik7C1JNW30zWuJi5VzcVzrr6gJSjazwtE1UccuzaIy MiIBfBlmhiRI631/1PZGPomdSt7i1srZGjqf/KM+/vfn3VZ/aKsa4yIhFnCxYCulW7Nr MO/lCsb6VXlMuZxWlTqykESm2kvzPFnLdInyfVR9XALa8NxWPD0ssMUCswNSWDmhPrVX sdAmpSL00tNCJWeIO32mDbjnpXg1c5gsBkfE5BUuo1p9VzfYJWdCnuJZ5DaOBrAR633f Gb0FHumpXzJJ/An/RD4DFWsMT99FghUX/K8DEk4/Gjtnyc1lYNNKU/754wzN0Nm5abeQ wpiQ== X-Gm-Message-State: ANhLgQ3BY7OchluNmw9bMbSNpE92Kvk1wNBWSctWbXNLfg2QzycOvCnY yTVcBFYnof6MYIj0IqxGOLQf9w== X-Google-Smtp-Source: ADFU+vuwf/QrgAe/wvSICyw0Gdo9gKfa2m7OL8eXk5v2Qj7EcVR2nCZJQDsnyzTNcT/joN8buhf6Ug== X-Received: by 2002:a67:2dc5:: with SMTP id t188mr3233479vst.3.1584643558942; Thu, 19 Mar 2020 11:45:58 -0700 (PDT) Received: from chatter.i7.local (node1.tor.k0nsl.org. [198.98.53.61]) by smtp.gmail.com with ESMTPSA id q3sm1612813vsp.8.2020.03.19.11.45.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Mar 2020 11:45:58 -0700 (PDT) Date: Thu, 19 Mar 2020 14:45:52 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: How to force stricter threading Message-ID: <20200319184552.4zxqket35fij64ua@chatter.i7.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20200309131539.wx56ntf7cb3gpozh@chatter.i7.local> <20200319072224.GA12221@dcvr> <20200319075820.GA13992@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200319075820.GA13992@dcvr> List-Id: On Thu, Mar 19, 2020 at 07:58:20AM +0000, Eric Wong wrote: > > So the "Patchwork summary for: linux-renesas-soc" message: > > > > https://lore.kernel.org/linux-renesas-soc/158229483332.12219.5639020605006542672.git-patchwork-summary@kernel.org/raw > > > > has the following header: > > > > References: <20200217101741.3758-1-geert+renesas@glider.be>, > > <20200218112414.5591-1-geert+renesas@glider.be>, > > <20200218112449.5723-1-geert+renesas@glider.be>, > > <20200219153929.11073-1-geert+renesas@glider.be>, > > <20200218132217.21454-1-geert+renesas@glider.be>, > > <20200217103251.5205-1-geert+renesas@glider.be> > > > > Which seems to have tied a bunch of unrelated threads together > > as one, similar to how a merge commit works in git but is > > unexpected and rare for mail threads. Thanks for tracking that down. > > But the thread rendering could be improved. What mutt does > > seems alright, but doesn't convey the "merge" scenario > > (I think) your bot was going for... > > Fwiw, RFC 5322 sec 3.6.4 states: > > Therefore, trying to form a "References:" field for a reply that > has multiple parents is discouraged; how to do so is not defined > in this document. > > So there's also that... I'll plan to stop adding these to the References: header and just give lore.kernel.org/r/ links. I don't think anyone would care and it will avoid this problem. Thanks again, -K