Received-SPF: pass (google.com: domain of linux-kernel+bounces-8556-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Thu, 21 Dec 2023 21:13:32 +0700
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Staging Drivers <linux-staging@lists.linux.dev>
Subject: Re: "Link in bio" instead of Link:/Closes: trailer
Message-ID: <ZYRIDDD_XR5HdVJu@archie.me>
References: <ZYQeZjN_3bPOdKKf@archie.me>
 <2023122112-rigging-january-7618@gregkh>
 <cc276c0e-99bb-4422-9771-d864db4287cb@gmail.com>
 <2023122129-twisty-mumble-c667@gregkh>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Ki5XL8WJal0E6W8j"
Content-Disposition: inline
In-Reply-To: <2023122129-twisty-mumble-c667@gregkh>


--Ki5XL8WJal0E6W8j
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 21, 2023 at 02:10:03PM +0100, Greg Kroah-Hartman wrote:
> 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 kern=
el
> > >> patch (touching drivers/staging/ of course to get her feet wet).
> > >> The patch supposes to fix a reported bug, with appropriate Fixes: ta=
g.
> > >> 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 re=
port),
> > >> 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 numbe=
r.
> > >>
> > >> Is such practice a good idea?
> > >=20
> > > No.
> >=20
> > why?
>=20
> Exactly, why?  What problem are you trying to solve here that has
> actually come up in any sort of frequency?

I was scratching my itch whether common social media practices (such as tha=
t's
being discussed here) can be applied to kernel development.

>=20
> "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.

Understand.

>=20
> 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.
>=20

That's the elegant way.

Thanks for explanation!

--=20
An old man doll... just what I always wanted! - Clara

--Ki5XL8WJal0E6W8j
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZYRICwAKCRD2uYlJVVFO
o2NQAP44SSFDD9rldUnNHUdaTP0OtROrwm9CyrQ4dUweSQqGQgEAl54b7oc1Uxbv
bfcLEe4kCoXXRrRH2wtyTHHG8jCUxwc=
=mAw/
-----END PGP SIGNATURE-----

--Ki5XL8WJal0E6W8j--