archive mirror
 help / color / mirror / Atom feed
From: Allison Randal <>
To: Steve Winslow <>
Subject: Re: [COX patch 1/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100
Date: Sat, 8 Jun 2019 16:50:32 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 6/6/19 8:39 AM, Steve Winslow wrote:
> I'd suggest this might be a good example of one where we want to (1)
> still add the SPDX tag, but (2) leave the existing notice text in
> place and wrap it in something like a NOTICE_BEGIN / NOTICE END block.
> The specific reference to individual / entity, plus the non-standard
> language about e.g. not admitting liability, makes me think that it's
> better to leave this in place. I do think GPL-2.0-or-later is the
> right tag but I'm inclined not to delete the notice altogether.

Agreed, these disclaimers contain specific information that can't be
deduced from the SPDX identifiers, so they should be kept. And wrapping
the custom disclaimers in some kind of machine readable tags makes
sense, though it's worth talking with SPDX to make sure that whatever we
add is actually useful.

I notice that there are only 22 total files, so we might be able to
shrink the set by contacting the original $PERSON and $CORP, where it's
still feasible to do so.


  parent reply	other threads:[~2019-06-08 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  9:53 [COX patch 0/2] Deep review of 'COX' disclaimers Thomas Gleixner
2019-06-06  9:53 ` [COX patch 1/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100 Thomas Gleixner
2019-06-06 12:39   ` Steve Winslow
2019-06-06 14:27     ` Richard Fontana
2019-06-06 15:14       ` Thomas Gleixner
2019-06-08 20:50     ` Allison Randal [this message]
2019-06-06  9:53 ` [COX patch 2/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 99 Thomas Gleixner
2019-06-06 12:41   ` Steve Winslow
2019-06-06 14:30     ` Richard Fontana
2019-06-11 14:24   ` Enrico Weigelt, metux IT consult
2019-06-11 15:40     ` Greg KH
2019-06-11 17:52       ` Thomas Gleixner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [COX patch 1/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox