All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Taylor Simpson <tsimpson@quicinc.com>,
	qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v2 1/2] linux-user: Move the SPDX license identifier to first line
Date: Thu, 4 Nov 2021 09:13:29 +0000	[thread overview]
Message-ID: <YYOkOW/REA0uXG2L@redhat.com> (raw)
In-Reply-To: <20211104071541.3813306-2-f4bug@amsat.org>

On Thu, Nov 04, 2021 at 08:15:40AM +0100, Philippe Mathieu-Daudé wrote:
> Tools consuming SPDX license identifiers benefit from having
> the SPDX tag in its own comment, not embedded with the license
> text. Move the tag to the first line.

Do you have an example of such a tool which has problems ?

AFAIK, guidance for adding SPDX tags merely says they should
be in a comment near the top of the file.

I wouldn't expect license scanners to care about the acutal
comment syntax. Proper tools would be designed to scan for
tags in *any* file format, so would be unlikely to be parsing
the C code comments at all. Rather scanners would be just
looking for the magic string "SPDX-License-Identifier" in
the file. Use of comments is merely to stop the C compiler
interpreting the tag.

It makes sense to have the SPDX tag as the first thing in
the file, but I don't see a compelling need to make it into
its own dedicated opened + closed comment, separately from
the license header comment.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-11-04  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  7:15 [PATCH v2 0/2] linux-user: Add GPL-2.0-or-later SPDX license identifier Philippe Mathieu-Daudé
2021-11-04  7:15 ` [PATCH v2 1/2] linux-user: Move the SPDX license identifier to first line Philippe Mathieu-Daudé
2021-11-04  9:13   ` Daniel P. Berrangé [this message]
2021-11-09 17:02     ` Warner Losh
2021-11-04  7:15 ` [PATCH v2 2/2] linux-user: Add GPL-2.0-or-later SPDX license identifier Philippe Mathieu-Daudé

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=YYOkOW/REA0uXG2L@redhat.com \
    --to=berrange@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=tsimpson@quicinc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.