From: "Drew DeVault" <sir@cmpwn.com>
To: "Jonathan Corbet" <corbet@lwn.net>
Cc: <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] submitting-patches.rst: streamline for git usage
Date: Mon, 31 Aug 2020 19:01:51 -0400 [thread overview]
Message-ID: <C5BK160QTFK2.1M3TL4ZI5HWW3@homura> (raw)
In-Reply-To: <20200831162641.16e90bb8@lwn.net>
Thanks for the feedback!
On Mon Aug 31, 2020 at 6:26 PM EDT, Jonathan Corbet wrote:
> - We have a document on configuring email clients for use in kernel
> development; we should be pointing there rather than to outside sites.
> There might well be a place for a pointer to useplaintext.email in
> Documentation/process/email-clients.rst, but that's a separate patch.
Yeah, I was wondering if this'd come up. There are an awful lot of email
clients and keeping an up-to-date list of instructions for configuring
plaintext is unfortunately an entire project in and of itself.
Will move to email-clients.rst in a separate patch for further
discussion.
> - In general we've been removing manual section numbers for the reasons
> amply demonstrated in this patch; maintaining them is a pain and, once
> you've gone through and changed them all, referring to sections by
> number doesn't work as well anymore. My own feeling is that they should
> come out.
Should this be split into its own patch?
> - Please don't just remove maintainer information like that. If it needs
> a new home, fine, find a new home for it. We have a nascent maintainers
> manual that could certainly use some help.
Totally fair, I'll look for a new home for this info.
prev parent reply other threads:[~2020-08-31 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:42 [PATCH] submitting-patches.rst: streamline for git usage Drew DeVault
2020-08-28 9:47 ` Jani Nikula
2020-08-28 12:31 ` Drew DeVault
2020-08-31 7:13 ` Jani Nikula
2020-08-31 22:26 ` Jonathan Corbet
2020-08-31 23:01 ` Drew DeVault [this message]
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=C5BK160QTFK2.1M3TL4ZI5HWW3@homura \
--to=sir@cmpwn.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox