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
Date: Thu, 21 Dec 2023 19:57:21 +0700 [thread overview]
Message-ID: <cc276c0e-99bb-4422-9771-d864db4287cb@gmail.com> (raw)
In-Reply-To: <2023122112-rigging-january-7618@gregkh>
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?
I'm confused...
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-12-21 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 11:15 "Link in bio" instead of Link:/Closes: trailer Bagas Sanjaya
2023-12-21 11:51 ` Greg Kroah-Hartman
2023-12-21 12:57 ` Bagas Sanjaya [this message]
2023-12-21 13:10 ` Greg Kroah-Hartman
2023-12-21 14:13 ` Bagas Sanjaya
2023-12-23 0:42 ` Theodore Ts'o
2023-12-24 8:43 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc276c0e-99bb-4422-9771-d864db4287cb@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox