From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: "Jonathan Corbet" <corbet@lwn.net>,
"Andy Whitcroft" <apw@canonical.com>,
"Joe Perches" <joe@perches.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Kai Wasserbäch" <kai@dev.carbon-project.org>,
"Thorsten Leemhuis" <linux@leemhuis.info>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, mptcp@lists.linux.dev
Subject: Re: [PATCH 1/2] docs: process: allow Closes tags with links
Date: Wed, 15 Mar 2023 19:28:58 +0100 [thread overview]
Message-ID: <5b92ed08-5a0c-7fcd-a75d-61cee3f28192@tessares.net> (raw)
In-Reply-To: <87zg8dop1f.fsf@meer.lwn.net>
Hi Jon,
On 15/03/2023 19:19, Jonathan Corbet wrote:
> Matthieu Baerts <matthieu.baerts@tessares.net> writes:
>
>> +In the same category as linking web pages, a special tag is also used to close
>> +issues but only when the mentioned ticketing system can do this operation
>> +automatically::
>> +
>> + Closes: https://example.com/issues/1234
>> +
>> +Please use this 'Closes:' tag only if it helps managing issues thanks to
>> +automations. If not, pick the 'Link:' one.
>
> So if there is a consensus for this, I can certainly apply the patch.
>
> I do think, though, that if we accept this tag, we should ask that it
> only be used for *public* trackers. A bunch of tags referring to
> internal trackers and such aren't going to be all that helpful.
Thank you for this feedback!
I agree, this should only refer to public bug trackers otherwise the
link is useless for most people.
In fact, that's what I wrote in submitting-patches.rst but I just
noticed I forgot to duplicate this into 5.Posting.rst. I can do that in
a v2 if there is no objection to allow this "Closes:" tag.
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
next prev parent reply other threads:[~2023-03-15 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 17:44 [PATCH 0/2] docs & checkpatch: " Matthieu Baerts
2023-03-15 17:44 ` [PATCH 1/2] docs: process: " Matthieu Baerts
2023-03-15 18:12 ` Konstantin Ryabitsev
2023-03-15 18:29 ` Matthieu Baerts
2023-03-15 18:19 ` Jonathan Corbet
2023-03-15 18:28 ` Matthieu Baerts [this message]
2023-03-15 19:12 ` Andrew Morton
2023-03-17 8:00 ` Bagas Sanjaya
2023-03-20 9:07 ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 2/2] checkpatch: " Matthieu Baerts
2023-03-16 9:22 ` [PATCH 0/2] docs & " Thorsten Leemhuis
2023-03-16 11:43 ` Matthieu Baerts
2023-03-16 17:30 ` Linus Torvalds
2023-03-17 16:58 ` Daniel Vetter
2023-03-17 18:41 ` Matthieu Baerts
2023-03-17 18:56 ` Konstantin Ryabitsev
2023-03-16 16:22 ` Konstantin Ryabitsev
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=5b92ed08-5a0c-7fcd-a75d-61cee3f28192@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=kai@dev.carbon-project.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=mptcp@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
all inboxes | Powered by JetHome®