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=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (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 CF40A1F619 for ; Mon, 9 Mar 2020 13:15:45 +0000 (UTC) Received: by mail-qv1-xf29.google.com with SMTP id fc12so4300470qvb.6 for ; Mon, 09 Mar 2020 06:15:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=jB62fMzUYHWc7hZG/jYRjs3/8eoR4NPgV1JC7ig4APA=; b=f2BQDW0DnzZgMw2bhODSgiPVn2UYIqMbYfbJTenbKUIg7UYAQ0bcrR4ZcpcRxngZZi lAdZjBwRMieW+/VQYtMVGhHQSkzMxylm6nR8GzLnVwWsut3M8N5ucpIHpH7AU1HKcEQk d3H88r4zkBm0IoxBwvdU2OhafnmSyKb+R0Ga4= 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:subject:message-id:mail-followup-to :mime-version:content-disposition; bh=jB62fMzUYHWc7hZG/jYRjs3/8eoR4NPgV1JC7ig4APA=; b=Pl7bGmznnRYUT7sikqf1Mp8YCDgjvLjNAWnv8hKLCe17GE779tzooj7pu/94tOG/rf 5f1jIioM4FMpvv8O2xTSPJz0me9Cpvw+em2FpdHqst1qNxLiNXctPp6qqANjV8yN/uFK wdTVkIgdd6uwyOpsNTMtQMk4W0S0wvHOjodnTiSjBYfqhKSARj6/yPYkmH7oOJVHHbcy OSOji4KnHWigHRhblp1HZZBbdrtGSrdEDvRFnDZ4eHE3nMEDZapdPMJWIjYupBoJ+rG+ j5t0ptiCVkyx2QyAfGfdPBODcjTH134wGCh4YEq76xHH0Gazi4KIf3j7r4zRmQ7VylQy Ng6w== X-Gm-Message-State: ANhLgQ0kHwyhC3NXsI5CVDm4sSi1Dp8YlW0RBhE4bFEfqTIU1m1sp6JT gZaGJB/KfhRCIkRToTBi9mTlQTJCVhnez+NA X-Google-Smtp-Source: ADFU+vuJ7HXN7gTUyciGsj8A7VRXXDzP7MqYOE7VLswwXEoaSBV67qnDl2rb2OLBYNKagiXs5EtBTw== X-Received: by 2002:ad4:4766:: with SMTP id d6mr7494383qvx.136.1583759743987; Mon, 09 Mar 2020 06:15:43 -0700 (PDT) Received: from chatter.i7.local (torex2.fissionrelays.net. [158.69.63.54]) by smtp.gmail.com with ESMTPSA id l13sm7734687qke.116.2020.03.09.06.15.42 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Mar 2020 06:15:43 -0700 (PDT) Date: Mon, 9 Mar 2020 09:15:39 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: How to force stricter threading Message-ID: <20200309131539.wx56ntf7cb3gpozh@chatter.i7.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: I think public-inbox currently does some heuristic-based threading, which may actually not be that useful. For example: https://lore.kernel.org/linux-renesas-soc/20200217101741.3758-1-geert+renesas@glider.be/ None of the [PATCH] messages have references or in-reply-to set, but for some reason they are threaded together. I can generally see this being useful for exact subject matches, but in this case all of the subjects are different (despite being similar). Is there a way to enforce stricter threading rules? -K