All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Matthieu Baerts" <matthieu.baerts@tessares.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: Matthieu Baerts <matthieu.baerts@tessares.net>,
	mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: process: allow Closes tags with links
Date: Wed, 15 Mar 2023 12:19:40 -0600	[thread overview]
Message-ID: <87zg8dop1f.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230314-doc-checkpatch-closes-tag-v1-1-1b83072e9a9a@tessares.net>

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.

jon

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: "Matthieu Baerts" <matthieu.baerts@tessares.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,
	Matthieu Baerts <matthieu.baerts@tessares.net>
Subject: Re: [PATCH 1/2] docs: process: allow Closes tags with links
Date: Wed, 15 Mar 2023 12:19:40 -0600	[thread overview]
Message-ID: <87zg8dop1f.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230314-doc-checkpatch-closes-tag-v1-1-1b83072e9a9a@tessares.net>

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.

jon

  parent reply	other threads:[~2023-03-15 18:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 17:44 [PATCH 0/2] docs & checkpatch: allow Closes tags with links Matthieu Baerts
2023-03-15 17:44 ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 1/2] docs: process: " Matthieu Baerts
2023-03-15 17:44   ` Matthieu Baerts
2023-03-15 18:12   ` Konstantin Ryabitsev
2023-03-15 18:12     ` Konstantin Ryabitsev
2023-03-15 18:29     ` Matthieu Baerts
2023-03-15 18:29       ` Matthieu Baerts
2023-03-15 18:19   ` Jonathan Corbet [this message]
2023-03-15 18:19     ` Jonathan Corbet
2023-03-15 18:28     ` Matthieu Baerts
2023-03-15 18:28       ` Matthieu Baerts
2023-03-15 19:12   ` Andrew Morton
2023-03-15 19:12     ` Andrew Morton
2023-03-17  8:00   ` Bagas Sanjaya
2023-03-17  8:00     ` Bagas Sanjaya
2023-03-20  9:07     ` Matthieu Baerts
2023-03-20  9:07       ` Matthieu Baerts
2023-03-15 17:44 ` [PATCH 2/2] checkpatch: " Matthieu Baerts
2023-03-15 17:44   ` Matthieu Baerts
2023-03-15 19:25   ` checkpatch: allow Closes tags with links: Tests Results MPTCP CI
2023-03-16  9:22 ` [PATCH 0/2] docs & checkpatch: allow Closes tags with links Thorsten Leemhuis
2023-03-16  9:22   ` Thorsten Leemhuis
2023-03-16 11:43   ` Matthieu Baerts
2023-03-16 11:43     ` Matthieu Baerts
2023-03-16 17:30     ` Linus Torvalds
2023-03-16 17:30       ` Linus Torvalds
2023-03-17 16:58       ` Daniel Vetter
2023-03-17 16:58         ` Daniel Vetter
2023-03-17 18:41         ` Matthieu Baerts
2023-03-17 18:41           ` Matthieu Baerts
2023-03-17 18:56           ` Konstantin Ryabitsev
2023-03-17 18:56             ` Konstantin Ryabitsev
2023-03-16 16:22   ` 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=87zg8dop1f.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --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=matthieu.baerts@tessares.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.