From: Jonathan Corbet <corbet@lwn.net>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
Randy Dunlap <rdunlap@infradead.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: add Co-Developed-by docs
Date: Wed, 7 Mar 2018 10:16:14 -0700 [thread overview]
Message-ID: <20180307101614.6722b592@lwn.net> (raw)
In-Reply-To: <1520222301-11874-3-git-send-email-me@tobin.cc>
On Mon, 5 Mar 2018 14:58:21 +1100
"Tobin C. Harding" <me@tobin.cc> wrote:
> When Co-Developed-by tag was added, docs were only added to
> Documention/process/5.Posting.rst and were not added to
> Documention/process/submitting-patches.rst
>
> Add documentation to Documention/process/submitting-patches.rst
Someday we should really pull those documents together into a coherent
whole so we don't have these weird synchronization issues. But it's much
easier to just apply this, so that's what I've done for now, with Willy's
comma tweak.
I'll leave the checkpatch part to Joe.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-07 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1520222301-11874-1-git-send-email-me@tobin.cc>
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 [this message]
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=20180307101614.6722b592@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--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=me@tobin.cc \
--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;
as well as URLs for NNTP newsgroup(s).