Messages in this thread | | | Date | Tue, 3 Jun 2014 09:19:49 +1000 | From | Dave Chinner <> | Subject | Re: [PATCH RFC 1/2] MAINTAINERS: Add "R:" designated-reviewers tag |
| |
On Mon, Jun 02, 2014 at 12:17:46PM -0700, Joe Perches wrote: > On Mon, 2014-06-02 at 12:09 -0700, josh@joshtriplett.org wrote: > > On Mon, Jun 02, 2014 at 12:05:17PM -0700, Joe Perches wrote: > > > On Mon, 2014-06-02 at 11:55 -0700, josh@joshtriplett.org wrote: > > > > this should go along with a change to > > > > get_maintainer.pl to add those folks to the CC list. > > > > > > Something like this: > > > > Yes, exactly. Given an appropriate commit message, > > Reviewed-by: Josh Triplett <josh@joshtriplett.org> > > That's the sort of patch where reviewing is > pretty useless. > > What it needs is testing, not reviewing. > > I tested it for all of 10 seconds.
From Documentation/SubmittingPatches:
" (c) While there may be things that could be improved with this submission, I believe that it is, at this time, (1) a worthwhile modification to the kernel, and (2) free of known issues which would argue against its inclusion. .....
A Reviewed-by tag is a statement of opinion that the patch is an appropriate modification of the kernel without any remaining serious technical issues."
So, for someone to say they have reviewed the code and are able to say it is free of known issues and has no remaining technical issues, they would have had to apply, compile and test the patch, yes?
i.e. Reviewed-by implies both Acked-by, Tested-by and that the code is technically sound.
Anyone using Reviewed-by without having actually applied and tested the patch is mis-using the tag - they should be using Acked-by: if all they have done is read the code in their mail program....
Cheers,
Dave. -- Dave Chinner david@fromorbit.com
| |