From: "W. Trevor King" <wking@tremily.us>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Signing off patches
Date: Sat, 18 Jan 2014 08:43:12 -0800 [thread overview]
Message-ID: <20140118164311.GN2647@odin.tremily.us> (raw)
In-Reply-To: <20140118160202.5fac3bda@TOMWIJ-GENTOO>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Sat, Jan 18, 2014 at 04:02:02PM +0100, Tom Wijsman wrote:
> - Reviewed-by: Reviewed the patch thoroughly
>
> What extra information does this tell us? This can be seen on ML.
I think the idea is that you shouldn't need to refer to an external
resource like the mailing list to understand the idea behind the
patch, or the amount of review it received. The body of the commit
message should summarize the consensus reached on the mailing list,
and these tags are basically standardized thank-you notes crediting
non-authors who were involved in that process. They don't have to go
on every patch, but if you want to mention somebody:
Reviewed-by: Random J Developer <random@developer.example.org>
Reviewed-by: Other R Developer <other@developer.example.org>
at the end of the commit message is easier to write and read than:
This patch was reviewed Random J Developer
<random@developer.example.org> and Other R Developer
<other@developer.example.org>.
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-18 16:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 13:20 [gentoo-portage-dev] Signing off patches Alexander Berntsen
2014-01-16 16:41 ` Alec Warner
2014-01-16 17:02 ` Alexander Berntsen
2014-01-16 16:45 ` W. Trevor King
2014-01-16 17:05 ` Alexander Berntsen
2014-01-16 17:11 ` W. Trevor King
2014-01-16 17:37 ` Alexander Berntsen
2014-01-16 17:24 ` Jesus Rivero (Neurogeek)
2014-01-16 17:44 ` Alexander Berntsen
2014-01-16 17:57 ` Jesus Rivero (Neurogeek)
2014-01-16 19:54 ` [gentoo-portage-dev] " Duncan
2014-01-16 20:07 ` W. Trevor King
2014-01-16 21:12 ` Alexander Berntsen
2014-01-18 6:44 ` [gentoo-portage-dev] " Mike Frysinger
2014-01-18 15:02 ` Tom Wijsman
2014-01-18 16:43 ` W. Trevor King [this message]
2014-01-18 22:57 ` Tom Wijsman
2014-01-18 23:24 ` W. Trevor King
2014-01-19 1:33 ` Tom Wijsman
2014-01-19 4:15 ` W. Trevor King
2014-01-20 2:09 ` Tom Wijsman
2014-01-20 2:32 ` W. Trevor King
2014-01-21 15:40 ` Tom Wijsman
2014-01-21 16:51 ` W. Trevor King
2014-01-21 16:59 ` Tom Wijsman
2014-01-21 17:20 ` W. Trevor King
2014-01-21 18:41 ` Tom Wijsman
2014-01-21 19:18 ` W. Trevor King
2014-01-21 19:22 ` Tom Wijsman
2014-01-21 19:45 ` W. Trevor King
2014-01-19 8:57 ` Mike Frysinger
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=20140118164311.GN2647@odin.tremily.us \
--to=wking@tremily.us \
--cc=gentoo-portage-dev@lists.gentoo.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