From: Jakub Kicinski <kuba@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: Docs for base maintainer expectations?
Date: Mon, 10 Jul 2023 13:46:23 -0700 [thread overview]
Message-ID: <20230710134623.659b3bc0@kernel.org> (raw)
In-Reply-To: <20230710-veteran-progeny-fee091cfff3c@spud>
On Mon, 10 Jul 2023 20:39:40 +0100 Conor Dooley wrote:
> It sounds almost as if you're looking for something to present to people
> when they add themselves as an `M:` entry against a driver, for when
> $company sends a patch w/ someone you've not really seen before?
That is exactly the use I have in mind.
next prev parent reply other threads:[~2023-07-10 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 18:52 Jakub Kicinski
2023-07-10 19:06 ` Conor Dooley
2023-07-10 19:22 ` Jakub Kicinski
2023-07-10 19:39 ` Conor Dooley
2023-07-10 20:46 ` Jakub Kicinski [this message]
2023-07-11 13:52 ` Jonathan Corbet
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=20230710134623.659b3bc0@kernel.org \
--to=kuba@kernel.org \
--cc=conor@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=workflows@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