From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPRLq-0006tv-82 for qemu-devel@nongnu.org; Wed, 21 Nov 2018 07:11:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPRAu-0004Iq-IB for qemu-devel@nongnu.org; Wed, 21 Nov 2018 07:00:10 -0500 Received: from mail-oi1-x244.google.com ([2607:f8b0:4864:20::244]:44593) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gPRAu-0004IP-61 for qemu-devel@nongnu.org; Wed, 21 Nov 2018 07:00:08 -0500 Received: by mail-oi1-x244.google.com with SMTP id p82-v6so4279282oih.11 for ; Wed, 21 Nov 2018 04:00:07 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1f31e8e0-cde2-db7a-56ae-26eb70bb13d9@redhat.com> References: <20181115192446.17187-1-minyard@acm.org> <20181115192446.17187-2-minyard@acm.org> <8add8514-f353-b914-78e8-e9f3e9be840d@redhat.com> <1f31e8e0-cde2-db7a-56ae-26eb70bb13d9@redhat.com> From: Peter Maydell Date: Wed, 21 Nov 2018 11:59:46 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2 01/12] i2c: Split smbus into parts List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= Cc: Corey Minyard , QEMU Developers , Paolo Bonzini , "Michael S . Tsirkin" , "Dr . David Alan Gilbert" , Corey Minyard On 20 November 2018 at 19:30, Philippe Mathieu-Daud=C3=A9 wrote: > On 20/11/18 16:47, Peter Maydell wrote: >> We don't yet use SPDX headers. (They're just a different and >> shorter way to write the license statement.) > > > Does that mean we can use them, or you rather prefer we don't? > > While they are machine parseable, I find them easier to understand than t= he > big chunk of legal text that sometime are not correctly written. It means that I'm not going to absolutely insist on dropping the line if somebody submits a patch with an SPDX tag, but I probably will mention that we don't use SPDX tags, and definitely I'm not going to ask for them. Overall I don't think there's much point in having them added to one or two files randomly. If we want them then we should consistently require them as policy. But that is work, and so I think we should not do that until/unless somebody (probably a corporate somebody) steps forward to make the argument for "this is why we should have them, we as a contributor to the project think they are worthwhile and a useful feature for us, and we will make the effort to add them, review that they are correct, update checkpatch to insist on tags for new files, etc". In other words, "if it ain't broke, don't fix it"; nobody is yet complaining that our current setup is broken. thanks -- PMM