lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240423-light-intrepid-aardwolf-7ebf85@lemur>
Date: Tue, 23 Apr 2024 13:04:32 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	workflows@...r.kernel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags
 after cutter '---' line

On Tue, Apr 23, 2024 at 08:00:16PM +0300, Jani Nikula wrote:
> Imagine the commit message Cc was named "Attn:" and handled
> appropriately. That probably reflects a lot of commit message Cc 
> usage.

This is especially the case for get_maintainer.pl purposes. Adding a Cc: 
in a commit message means that this person will be included on patches 
referencing this commit (e.g. via Fixes:).

-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ