Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B32B1C77B78 for ; Wed, 26 Apr 2023 17:01:51 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 43A5985723; Wed, 26 Apr 2023 19:01:49 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="MsrodclC"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 2E38985F06; Wed, 26 Apr 2023 19:01:48 +0200 (CEST) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by phobos.denx.de (Postfix) with ESMTP id 9E57E8564F for ; Wed, 26 Apr 2023 19:01:45 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=emohandesi@linux.microsoft.com Received: from [192.168.0.167] (c-73-183-134-76.hsd1.tx.comcast.net [73.183.134.76]) by linux.microsoft.com (Postfix) with ESMTPSA id 2F46021C33C0 for ; Wed, 26 Apr 2023 10:01:44 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 2F46021C33C0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1682528504; bh=1mDND1UFYDD/03ORriA1aE9ZaQVy2hy6k8MqQgnhh24=; h=Date:To:From:Subject:From; b=MsrodclC7y4imoTiWVqnh/DQUDNE2x5UJK66PbXuhhgHYiDhKB0U+9m/kYgWm88M6 KCEDrm0deLtfp5Sdj9Z37FOkWvR34Aip87JRr+8faMLhRhpHelBTUm4GTKFWrADMHr 60ek6VG1nr4e1vYJQ3aO5caMhRBbDzNJ7N0n6zxY= Message-ID: <74ec6e81-1239-1089-6a6f-30e21b7f5753@linux.microsoft.com> Date: Wed, 26 Apr 2023 12:01:43 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 To: u-boot@lists.denx.de Content-Language: en-US From: Ehsan Mohandesi Subject: Should different versions of a patch be threaded to each other? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean The following discusses the threading of patches. https://u-boot.readthedocs.io/en/latest/develop/sending_patches.html#sending-updated-patch-versions I see the following mentioned there. "Make sure that your mailer adds or keeps correct In-reply-to: and References: headers, so threading of messages is working and everybody can see that the new message refers to some older posting of the same topic. Uncommented and un-threaded repostings are extremely annoying and time-consuming, as we have to try to remember if anything similar has been posted before, look up the old threads, and then manually compare if anything has been changed, or what." Does it mean that when a newer version of a patch is sent, it should keep a pointer to the previous version's thread by using the In-reply-to field? I have hardly seen anyone doing this.