linux-kernel - Re: "Link in bio" instead of Link:/Closes: trailer

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 21 Dec 2023 12:51:16 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Jakub Kicinski <kuba@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Staging Drivers <linux-staging@...ts.linux.dev>
Subject: Re: "Link in bio" instead of Link:/Closes: trailer

On Thu, Dec 21, 2023 at 06:15:50PM +0700, Bagas Sanjaya wrote:
> Hi all,
> 
> Let's say that there is a content creator who submits her first kernel
> patch (touching drivers/staging/ of course to get her feet wet).
> The patch supposes to fix a reported bug, with appropriate Fixes: tag.
> But instead of using Link: or Closes: tag to the actual bug report in
> the patch, she instead writes "Link to the bug report in my bio", as
> it is the norm in social media world. Here in the context, her bio is
> LinkedIn profile (IDK if there is a way to add arbitrary link there).
> The link in LinkedIn profile, when clicked, will list many links
> (including her usual social media campaigns and of course the bug report),
> which makes reviewers confused about which link to the bug report she
> means. In some cases, she may disambiguate by saying in the patch,
> "Link to the bug report no. 99", to refer to the specific link number.
> 
> Is such practice a good idea?

No.