Re: RFC: reviewer's statement of oversight

Oleg Verych
2007-10-08T23:06:19Z

* Mon, 8 Oct 2007 17:38:52 -0400
>
> On Mon, Oct 08, 2007 at 01:33:38PM -0700, H. Peter Anvin wrote:
>> Uhm, no. There is no reason an "unimportant" person couldn't review a
>> patch, and therefore perform a potentially highly valuable service to
>> the maintainer.
>>
>> None of these are indicative of the authority of the person acking,
>> reviewing, testing, or nacking. That's only as good as the trust in the
>> person signing.
>
> I would tend to agree. Right now I think the problem is that we are
> getting too little reviews, not enough. And someone who reviews
> patches, even if unknown, could be building up expertise that
> eventually would make them a valued developer, even while they are
> doing us a service.

Experience of convincing experienced patch author, that some things in
the patch are wrong :)

[]
> We could ask reviewers to include a URL to an LKML archive of their
> review, to make it easier to find a review of a patch so later on
> people can judge how effective they their review was.

I vote for more little summaries in the `Subject'(again). Long, boring
threads with whole threading part of screen being empty due to same
subjects isn't fun, when some of thousands of messages can have
interesting stuff inside.

And it's easy not only for mailing list readers now, and for archive
readers also; readers of the www search results (who ever that may be):

google.com/search?q=reviewed+crashkernel

First hit on the review of the patch, i happened to make. And i just
thought "hell, just string parsing, what can be more simply?", yet there
was productive discussion and bug fixing. After i saw convincing
statements about testing, i've placed review mark. Though i'm really
"unimportant" random hacker.
--
-o--=O`C
#oo'L O
<___=E M