Received: by 2002:ab2:1689:0:b0:1f7:5705:b850 with SMTP id d9csp1222210lqa; Mon, 29 Apr 2024 01:45:02 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCUFXGs6IkUWI2GO34eLvhiX+GMipJGbN14h7zofhqSljLNeUA62YNqDuMUcaRwbMx7jaG0L6+VDpOj4pPWe9cRDJiaeA7sNPCgre61CgQ== X-Google-Smtp-Source: AGHT+IFcq1rwagi1wRb8OSwprIlpp4q8M+fVm3DIeGkoidwygF+mq8wtX+zGwFd3N6MkeRky6Jcv X-Received: by 2002:a25:e4c5:0:b0:de5:f0ef:7898 with SMTP id b188-20020a25e4c5000000b00de5f0ef7898mr2615875ybh.20.1714380301756; Mon, 29 Apr 2024 01:45:01 -0700 (PDT) Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id t24-20020a05620a0b1800b00790f8848d66si1260856qkg.69.2024.04.29.01.45.01 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 Apr 2024 01:45:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel+bounces-161922-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@intel.com header.s=Intel header.b=KIUiM9cO; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-161922-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-161922-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 617981C20BFD for ; Mon, 29 Apr 2024 08:45:01 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A630817BCA; Mon, 29 Apr 2024 08:44:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=intel.com header.i=@intel.com header.b="KIUiM9cO" Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AE89B1773A; Mon, 29 Apr 2024 08:44:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714380293; cv=none; b=H/3/s5TNERzj+HIg+i3gnn+i8knarmcl80A2QdDdp/ydTEU8Nc9T9H7/E5Bl6CvfVgLzNHPyhqWtFYou1jcYSoNV+JSVUk1cG+hujbKrUmpjEa7ptzyRkCkRUOQK0spLnY6zftQmOyVAieFNiD1r7mrDF9j5TFXilYpgLg2sgOw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714380293; c=relaxed/simple; bh=hKl+ddFweiXgM/nNkFP9yir7ry8EsSWt9YFq0r39Cyw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BgyI3Cf4JuS7Xr6sARfBCqHq6u2geeWxlGl7R8bHEG1WfvjB+ghoBWjazU2ogDM3N0YZq3T5C/v07+1xbClsM1uHgckK72zxF9z7KK7yLfBizxESRdiLvyQioU0xx/CaqEuEZP8Ic7qfs81+rPY7GtKOMi/biaYNTAKHazEydIs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=KIUiM9cO; arc=none smtp.client-ip=198.175.65.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1714380292; x=1745916292; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=hKl+ddFweiXgM/nNkFP9yir7ry8EsSWt9YFq0r39Cyw=; b=KIUiM9cOvnxQv6HvFMIuwqQUcOaTK/AQGkkt76LX+nrdqEahoXagYicB KYEC23URVRYe3i2J9ROuz18ohN4zwpQijpIYRt5jY/cdyh/lr1WsFNxoQ Yx9oP0+Gf4vuWUef1d0Xzzj0mWb612uIoaBNMBRNwvwWaY+HElvAavlc4 DW92YNJQPHhoTa3L3T0ni0avxT8bLpxeAEzg19g7tFhxvtlHvU2rQpusp fjzCFKCHHbGIHZpovRKGRM8EaTY0yWt5X5YL46wwy95mQ7SZymt+YUFjU Ic0bgqeCUMAR7gjZeNWZrhfWgrsiD0X1QFj73mjiE7ivLw2Lbs31Xc3rY w==; X-CSE-ConnectionGUID: 9lBOt3H3Rw2wD1pTkIgO4A== X-CSE-MsgGUID: ZadS+pj2SxOBvuiP8CGSDw== X-IronPort-AV: E=McAfee;i="6600,9927,11057"; a="13807782" X-IronPort-AV: E=Sophos;i="6.07,239,1708416000"; d="scan'208";a="13807782" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by orvoesa107.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Apr 2024 01:44:51 -0700 X-CSE-ConnectionGUID: M44kx3PiThKqJrrPXi7A9Q== X-CSE-MsgGUID: lRoWaxVfSaKaTaCFY79CSQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.07,239,1708416000"; d="scan'208";a="30702120" Received: from smile.fi.intel.com ([10.237.72.54]) by fmviesa004.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Apr 2024 01:44:49 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97) (envelope-from ) id 1s1Mcx-00000002G9e-1CEx; Mon, 29 Apr 2024 11:44:47 +0300 Date: Mon, 29 Apr 2024 11:44:47 +0300 From: Andy Shevchenko To: Krzysztof Kozlowski Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Jonathan Corbet Subject: Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line Message-ID: References: <20240423132024.2368662-1-andriy.shevchenko@linux.intel.com> <20240423132024.2368662-3-andriy.shevchenko@linux.intel.com> <927c40c5-cfd7-4a22-a9c6-7b6f9592e4b0@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <927c40c5-cfd7-4a22-a9c6-7b6f9592e4b0@kernel.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Mon, Apr 29, 2024 at 09:35:18AM +0200, Krzysztof Kozlowski wrote: > On 23/04/2024 15:19, Andy Shevchenko wrote: > > The recommendation is based on the following rationale: > > > > - it makes the commit messages much cleaner and easy to read, especially > > on the screens of the mobile devices; > > > > - it reduces resources (memory, time, energy) to retrieve all these > > headers, which are barely needed by a mere user, as for automation > > they will be still available via mail archives, such as > > https://lore.kernel.org, assuming the Link: or Message-ID tag is > > provided. > > > > Let's be environment friendly and save the planet! .. > > +It's recommended to locate the additional Cc: tags after the cutter '---' line > > +in the patches as it makes sure the commit message won't be polluted with them. > > +At the same time they will be available via email headers on the mail archives, > > +such as https://lore.kernel.org. > > Manually added useful Cc-tags should be kept in commit msg, because it > annotates who could be interested in the patch. > > The problem is that people put output of get_maintainers.pl as Cc to the > commit list. This is 100% redundant because it can be recreated any > given time with 100% accuracy (for given kernel tree). Therefore I would > propose to rephrase it to something: > > ==== > It is recommended to not add autogenerated scripts/get_maintainer.pl > CC-entries into the commit msg, but keep them under cutter '---'. There > is no single need to store automated output of get_maintainers.pl in the > git log. It can be easily re-created at any given time, thus its > presence in the git history is redundant and obfuscates the log. Right, but still even for non-automated output it might (may) be redundant, however I can go for this compromise as most of the Cc indeed duplicate the output of get_maintainer.pl. -- With Best Regards, Andy Shevchenko