From: "Tobin C. Harding" <me@tobin.cc>
To: Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Tobin C. Harding" <me@tobin.cc>, Joe Perches <joe@perches.com>,
Randy Dunlap <rdunlap@infradead.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject:
Date: Mon, 5 Mar 2018 14:58:19 +1100 [thread overview]
Message-ID: <1520222301-11874-1-git-send-email-me@tobin.cc> (raw)
Subject: [PATCH 0/2] Resolve Co-Developed-by issues
Recently tag Co-Developed-by was added (via a patch to
Documention/process/5.Posting.rst).
see https://lkml.org/lkml/2017/11/16/257
There has already been some discontent expressed over this tag.
A recent patch using the tag generated this response from akmp (on LKML)
I prefer not to include tags which aren't listed in
Documentation/process/submitting-patches.rst, but I now see that
some bright spark added Co-Developed-by: to
Documentation/process/5.Posting.rst, so the two files are a)
duplicative and b) out of sync
Also, there has been comment over the use of the second capitalized
character 'D'.
This patch set attempts to either resolve this issue or bury it for
good.
May the bike shedding begin :)
Joe Perches (1):
checkpatch: add check for tag Co-Developed-by
Tobin C. Harding (1):
docs: add Co-Developed-by docs
Documentation/process/submitting-patches.rst | 9 ++++-
scripts/checkpatch.pl | 58 +++++++++++++++++-----------
2 files changed, 42 insertions(+), 25 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-05 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 3:58 Tobin C. Harding [this message]
2018-03-05 3:58 ` [PATCH 1/2] checkpatch: add check for tag Co-Developed-by Tobin C. Harding
2018-03-05 19:29 ` Joe Perches
2018-03-05 3:58 ` [PATCH 2/2] docs: add Co-Developed-by docs Tobin C. Harding
2018-03-05 12:11 ` Matthew Wilcox
2018-03-05 21:24 ` Tobin C. Harding
2018-03-07 17:16 ` Jonathan Corbet
2018-03-07 18:07 ` Dominik Brodowski
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=1520222301-11874-1-git-send-email-me@tobin.cc \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
/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