From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Neil Brown <neilb@suse.de>
Subject: Re: [PATCH] Documentation/patch-tags V2
Date: Tue, 9 Oct 2007 10:11:26 -0700 [thread overview]
Message-ID: <20071009101126.8b837436.randy.dunlap@oracle.com> (raw)
In-Reply-To: <32507.1191949182@lwn.net>
On Tue, 09 Oct 2007 10:59:42 -0600 Jonathan Corbet wrote:
> Here's a new version of the patch-tags document. I've incorporated
> comments from Randy Dunlap, Stefan Richter, and Neil Brown, though I
> have retained, for now, the more verbose process discussion that Neil
> didn't like.
>
> Comments?
>
> jon
>
> --
>
> Document the tags used with kernel patches
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
>
> diff --git a/Documentation/patch-tags b/Documentation/patch-tags
> new file mode 100644
> index 0000000..d955fa2
> --- /dev/null
> +++ b/Documentation/patch-tags
> @@ -0,0 +1,81 @@
> +Patches headed for the mainline may contain a variety of tags documenting
> +who played a hand in (or was at least aware of) its progress. All of these
s/its/their/
> +tags have the form:
> +
> + Something-done-by: Full name <email@address> [optional random stuff]
> +
> +These tags are:
> +
[snip]
> +Tested-by: The patch has been successfully tested (in some
> + environment) by the person named. This tag informs
> + maintainers that some testing has been performed and
> + ensures credit for the testers.
?: and provides a means to locate testers for future patches.
> +
> +
> +----
> +
> +Reviewer's statement of oversight, v0.02
[snip]
---
~Randy
prev parent reply other threads:[~2007-10-09 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 16:59 [PATCH] Documentation/patch-tags V2 Jonathan Corbet
2007-10-09 17:11 ` Randy Dunlap [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=20071009101126.8b837436.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stefanr@s5r6.in-berlin.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