From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5145C072B5 for ; Fri, 24 May 2019 16:29:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 868E620851 for ; Fri, 24 May 2019 16:29:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="MRfOE1pM"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=lohutok.net header.i=@lohutok.net header.b="bhBHCHfl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390365AbfEXQ3N (ORCPT ); Fri, 24 May 2019 12:29:13 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:62622 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390314AbfEXQ3M (ORCPT ); Fri, 24 May 2019 12:29:12 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 98C06152A72; Fri, 24 May 2019 12:29:11 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to:cc :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=cPGl9XpLskqn ELTpPkfZw9ufwcg=; b=MRfOE1pMCgJzTUpa7OaYcvpXJdsqtvjfUr8wSKQ+VXAo yyfsD0ZpgmISbmYDWDkEfMpQ7+7s6505+h30z4gDJtdtZ4HDkKmmZB2nhmeuJi4D LDaTaSu3rqAh/B0hx2iZlI9D3IvVaYY5hVC459A22aX10MouqJ3YLJcExbzM2fg= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9026D152A71; Fri, 24 May 2019 12:29:11 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lohutok.net; h=subject:to:cc:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=2018-11.pbsmtp; bh=uLA4ZejLPCpKPpgiOnFh6VJ3/+bjWqCyTnyivbEP58s=; b=bhBHCHfluKlurdVtAV2ZLDxQCcLsWDlszJ9kstcdDXPqp3YrNg1OztGa51y/r6cPcZdY6gAgS+hzxhCUAg2tbzuT5mqnYiIV0T6pfo82oJs/IHPI65tzce5Zhc8fDC5SSXd9AL4j4R3km6SMrTrQmwwBpW8voV1XMRqiCTfQDhQ= Received: from [10.0.0.75] (unknown [24.47.52.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 0889C152A70; Fri, 24 May 2019 12:29:11 -0400 (EDT) Subject: Re: [patch 05/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 80 To: Greg KH Cc: Richard Fontana , linux-spdx@vger.kernel.org References: <20190520075121.768803433@linutronix.de> <20190520075211.039040246@linutronix.de> <20190522131836.GA28920@kroah.com> <20190524055532.GA2428@kroah.com> From: Allison Randal Message-ID: <14f371ad-ad4b-92c6-e5b1-c3f4aa2abb4d@lohutok.net> Date: Fri, 24 May 2019 12:29:10 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <20190524055532.GA2428@kroah.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 0F9CC9F8-7E41-11E9-B60F-46F8B7964D18-44123303!pb-smtp1.pobox.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org On 5/24/19 1:55 AM, Greg KH wrote: > On Thu, May 23, 2019 at 10:21:57PM -0400, Richard Fontana wrote: >> >> I assume it's okay to put the "Reviewed-by:" at the top of the reply though? > > It's not the nicest, as you should trim the email and not quote the > whole large patch, but we can live with it for now. I've been a developer on so many different open source projects, that I've adopted the "When in Rome" Rule, following whatever formal or informal patterns the project prefers. Here, I'd expect that to be: https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst But, that doc doesn't actually say where to put the "Reviewed-by" line in a reply email, so the tools will pick it up. As far as I can tell from lkml, the r-b line can go anywhere in the reply, so I'll experiment with that on today's batch. But, really, I am totally happy to precisely follow whatever pattern you prefer, so just let us know. We are guests in your development workflow, so it makes more sense for us to adapt to you, than for you to adapt to us. :) Allison