ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful
Date: Mon, 8 Jul 2019 13:59:50 +0200	[thread overview]
Message-ID: <20190708115949.GC1050@kunai> (raw)
In-Reply-To: <CAMuHMdUVtz6_3-9_+QLRWt6x7fauvA0K4p77eOcyVWo_oO9g5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]

Hi Geert,

> > 1) we need a better distinction between Acked-by: and Reviewed-by: and encourage
> >    stricter use of that
> 
> Before we had "Reviewed-by", "Acked-by" meant "looks OK to me".
> Then we got "Reviewed-by" for more thorough reviews.

This is what still makes most sense to me. You can express e.g. that you
like a patch series and approve the general approach taken but haven't
gone for the gory details -> Acked-by (a short explaining paragraph
would make sense, then, too)

Is that old fashioned?

Acked-by only for maintainers doesn't make sense to me. Neiher does when
Acked-by has a different meaning for maintainers and non-maintainers.

> > 3) trivial patches should rather get Acked-by
> 
> These days when given by a maintainer, "Acked-by" means that the
> maintainer is happy for the patch going in through another subsystem.

I still see this as a "looks OK to me" variant. A patch is good enough
to enter my subsystem. Sometimes, I also use "Reviewed-by" for this,
namely when I thoroughly looked at (=reviewed) a patch.

> > 2) A short paragraph will usually do. Of course, trust helps a lot, but it
> > doesn't solve everything. Trusted people can be in a hurry, too, etc. And for
> > people I don't know, the plain tag doesn't tell me much. Examples for short
> > descriptions: "I can't say much about the media part, but the I2C part is
> > proper" or "I also checked the documentation and I think this is a good
> > approach to overcome the issue" or "All my concerns in the preceding
> > discussions have been addressed"
> 
> Definitely good to have, but hard to enforce, without making the process
> heavier.

As I wrote before, I don't want to enforce that. But spread the word
that it is good to have and should be done and common sense should apply.

> I have a fifth thesis: many people (incl. guilty me) browse quickly
> through many patches flying by on mailing lists, but don't always go to
> the effort of replying if they don't see something wrong immediately.
> This means we don't catch a share of the reviews happening.

For me, Acked-by would do here.

Thanks,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-08 11: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 [this message]
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
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=20190708115949.GC1050@kunai \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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