From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 4551F976 for ; Wed, 28 May 2014 20:22:46 +0000 (UTC) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7EF7B2034E for ; Wed, 28 May 2014 20:22:45 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id hz1so11554462pad.16 for ; Wed, 28 May 2014 13:22:45 -0700 (PDT) From: Dmitry Torokhov To: ksummit-discuss@lists.linuxfoundation.org Date: Wed, 28 May 2014 13:22:42 -0700 Message-ID: <1442785.duAJunkqTR@dtor-d630.eng.vmware.com> In-Reply-To: <20140528201228.GA14247@cloud> References: <1400925225.6956.25.camel@dabdike.int.hansenpartnership.com> <20140528201228.GA14247@cloud> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: James Bottomley Subject: Re: [Ksummit-discuss] Reforming Acked-by (was Re: [TOPIC] Encouraging more reviewers) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wednesday, May 28, 2014 01:12:28 PM josh@joshtriplett.org wrote: > On Wed, May 28, 2014 at 06:48:47PM +0000, Paul Walmsley wrote: > > Also long-overdue is a clarification on exactly what "Acked-by" means. > > Right now it is being used for at least two distinct and > > mutually-incompatible purposes: > > > > 1. A maintainer A for code affected by a patch, who is distinct from a > > maintainer B queuing a patch, has reviewed the patch and has cleared it as > > being OK for maintainer B to send upstream > > > > 2. A casual review has been done by someone who is not a maintainer for > > the code in question > > > > What I would propose is to have the first use replaced by a new tag, > > "Maintainer-acked-by:", and the second use abolished, along with > > "Acked-by:", and replaced by "Reviewed-by:". > > In practice, (2) seems to have been mostly replaced by "Reviewed-by"; I > rarely see Acked-by used for cases other than (1): "I'm the maintainer > or an affected subsystem developer, I approve of this patch, but I don't > intend to take it through my own tree." I believe we still need a separate mark for casual review. I can scan a patch and find a few item that i might now like, but if I do not do full review in the first pass and then again after the issues that have been pointed out have been corrected I won't be stamping "Reviewed-by" on the patch. Nitpicked-by? :) -- Dmitry