From: Randy Dunlap <rdunlap@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>, Olof Johansson <olof@lixom.net>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful
Date: Tue, 16 Jul 2019 20:59:25 -0700 [thread overview]
Message-ID: <bf269ea7-6a9c-25db-5b97-958d9e15bddd@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1907170026200.1767@nanos.tec.linutronix.de>
On 7/16/19 3:27 PM, Thomas Gleixner wrote:
> On Tue, 16 Jul 2019, Olof Johansson wrote:
>> On Tue, Jul 16, 2019 at 2:16 PM Wolfram Sang <wsa@the-dreams.de> wrote:
>>>
>>>
>>>> Even if we agree on a set of new tags the usage will still be based on
>>>> individual interpretation, which brings us back to square one.
>>>
>>> I agree. New tags won't help us much.
>>>
>>>> So no, let's just accept that these things are subjective and apply common
>>>> sense to make the best use of them.
>>>
>>> I meanwhile do think, though, that for "best use" it will be helpful to
>>> add my Rev-by to my SoB when I really did a full review (and not just
>>> trusted other reviewers). To properly document the process of a patch.
>>
>> I don't see how this is bringing much value. You picked up the patch,
>> and if you did so without looking closely at it, the end result is the
>> same: You're likely to be on the line for dealing with issues.
>>
>> The only thing a "S-o-b" without "R-b" would bring is "It's not my
>> fault that stuff broke" -- but it still is since your name is on it,
>> and that's not something that adds value for the project as a whole.
>
> Right, if you commit it then you are responsible for it. It does not matter
> whether you reviewed it yourself or relied on someone else review.
It's a bit amazing (and scary) that this is even being discussed (as though
it's unknown) after these many years.
--
~Randy
next prev parent reply other threads:[~2019-07-17 3:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 14:27 Wolfram Sang
2019-07-06 16:52 ` Leon Romanovsky
2019-07-06 17:17 ` Wolfram Sang
2019-07-08 10:47 ` Jan Kara
2019-07-08 11:47 ` Wolfram Sang
2019-07-15 16:11 ` Mauro Carvalho Chehab
2019-07-08 11:21 ` Geert Uytterhoeven
2019-07-08 11:59 ` Wolfram Sang
2019-07-15 15:58 ` Mauro Carvalho Chehab
2019-07-15 17:00 ` Theodore Y. Ts'o
2019-07-15 17:11 ` Mauro Carvalho Chehab
2019-07-16 21:26 ` Wolfram Sang
2019-08-17 21:35 ` Paul Walmsley
2019-08-19 6:57 ` Jan Kara
2019-08-19 7:06 ` Jiri Kosina
2019-08-19 7:06 ` Julia Lawall
2019-08-19 8:04 ` Jan Kara
2019-08-19 8:13 ` Julia Lawall
2019-08-20 10:22 ` James Bottomley
2019-08-19 8:26 ` Thomas Gleixner
2019-08-19 16:16 ` Christian Brauner
2019-08-19 19:04 ` Thomas Gleixner
2019-08-19 21:03 ` Christian Brauner
2019-07-08 14:57 ` Mark Brown
2019-07-14 9:35 ` Jonathan Cameron
2019-07-14 10:13 ` Thomas Gleixner
2019-07-15 9:10 ` Rafael J. Wysocki
2019-07-16 21:16 ` Wolfram Sang
2019-07-16 21:57 ` Olof Johansson
2019-07-16 22:27 ` Thomas Gleixner
2019-07-17 3:59 ` Randy Dunlap [this message]
2019-07-17 7:31 ` Wolfram Sang
2019-07-17 16:05 ` Linus Walleij
2019-07-17 16:40 ` Wolfram Sang
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=bf269ea7-6a9c-25db-5b97-958d9e15bddd@infradead.org \
--to=rdunlap@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lixom.net \
--cc=tglx@linutronix.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