Received-SPF: pass (google.com: domain of linux-kernel+bounces-8267-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Date: Thu, 21 Dec 2023 18:15:50 +0700
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Staging Drivers <linux-staging@lists.linux.dev>
Subject: "Link in bio" instead of Link:/Closes: trailer
Message-ID: <ZYQeZjN_3bPOdKKf@archie.me>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="IOy+elnsY4ZQ97PS"
Content-Disposition: inline


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

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?

Thanks.

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

--IOy+elnsY4ZQ97PS
Content-Type: application/pgp-signature; name="signature.asc"

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

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZYQeYgAKCRD2uYlJVVFO
oyl4AQDFmpF+DPHFIzFJyphKvMA2JTCPGUl3MdlFX7MWpYCtCgD+KAmls0qYS/hC
3dMHV3vv6tOClNLTn4amwF/0384xzQo=
=Vqzw
-----END PGP SIGNATURE-----

--IOy+elnsY4ZQ97PS--