All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-doc@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
	Joe Perches <joe@perches.com>
Subject: Re: [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by"
Date: Thu, 22 Feb 2018 10:40:24 -0700	[thread overview]
Message-ID: <20180222104024.60408a75@lwn.net> (raw)
In-Reply-To: <20180222003749.GA4724@beast>

On Wed, 21 Feb 2018 16:37:50 -0800
Kees Cook <keescook@chromium.org> wrote:

> As recently pointed out by Linus, "Root-caused-by" is a good tag to include
> since it can indicate significantly more work than "just" a Reported-by.
> This adds it and "Suggested-by" (which was also missing) to the documented
> list of tags. Additionally updates checkpatch.pl to match the process docs.

So I'm not really opposed to this, but I do wonder if we really need to
make a catalog of all the tags that might appear.  A quick grep turns up
stuff like:

	Niced-by
	Based-on-a-patch-by
	Debugged-by
	Requested-by
	Despised-by
	Improvements-by
	Tracked-by
	Analyzed-by
	Bisected-by
	Okay-ished-by
	\o/-by
	Pointed-at-by
	Brown-paper-bag-to-be-worn-by
	Not-longer-ranted-at-by
	Rightfully-ranted-at-by
	Helped-by
	Architected-by
	Also-posted-by
	Complained-about-by
	Mehed-by
	Reminded-by
	Actually-written-by
	Generated-by
	Historical-research-by

Some of these are arguably more useful than others, but I'm not sure we
want to bother documenting even an often-used subset of them.

That said, we can add this one; I'll take the patch if I get an ack from
Joe.

jon

  parent reply	other threads:[~2018-02-22 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  0:37 [PATCH] doc: process: Add "Root-caused-by" and "Suggested-by" Kees Cook
2018-02-22  2:13 ` Joe Perches
2018-02-22  2:16   ` Kees Cook
2018-02-22  4:43 ` Randy Dunlap
2018-02-22  6:03   ` Kees Cook
2018-02-22 17:29     ` Randy Dunlap
2018-02-22 17:40 ` Jonathan Corbet [this message]
2018-02-22 23:52   ` Joe Perches

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=20180222104024.60408a75@lwn.net \
    --to=corbet@lwn.net \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.