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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2023122129-twisty-mumble-c667@gregkh>
Date: Thu, 21 Dec 2023 14:10:03 +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 07:57:21PM +0700, Bagas Sanjaya wrote:
> On 12/21/23 18:51, Greg Kroah-Hartman wrote:
> > 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.
> 
> why?

Exactly, why?  What problem are you trying to solve here that has
actually come up in any sort of frequency?

"Link: " is something that should be used to point to a well-known and
stable reference for any future things, like red hat's bugzilla, or
lore.kernel.org.  It's not for random social-media link reputation
spamming, sorry.

The "proper" way to handle this is to have in your Linked-in, or
whatever social media site you like, a list of your committed patches in
the git.kernel.org tree, don't polute the kernel log please.

greg k-h