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=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 3B18BC43613 for ; Mon, 24 Jun 2019 09:45:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1221E2054F for ; Mon, 24 Jun 2019 09:45:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726731AbfFXJpV (ORCPT ); Mon, 24 Jun 2019 05:45:21 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:52590 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726481AbfFXJpV (ORCPT ); Mon, 24 Jun 2019 05:45:21 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hfLXL-0006LV-3q; Mon, 24 Jun 2019 11:45:19 +0200 Message-ID: <90ccc515bb26b212b537fc1b0287afaa0f86fdf8.camel@sipsolutions.net> Subject: Re: [PATCH] Add SPDX identifiers From: Johannes Berg To: yegorslists@googlemail.com, linux-wireless@vger.kernel.org Date: Mon, 24 Jun 2019 11:45:17 +0200 In-Reply-To: <20190620130148.1674-1-yegorslists@googlemail.com> (sfid-20190620_150200_364028_4753B2C0) References: <20190620130148.1674-1-yegorslists@googlemail.com> (sfid-20190620_150200_364028_4753B2C0) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-3.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, 2019-06-20 at 15:01 +0200, yegorslists@googlemail.com wrote: > From: Yegor Yefremov > > Software Package Data Exchange identifiers help to detect source file > licenses and hence simplify the FOSS compliance process. Well that's nice and all, but it's also wrong. You haven't included any documentation that says what the SPDX identifier, and specifically the "ISC" tag means in the context of the project, and it's not even the same license text as on spdx.org. johannes