linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Fontana <rfontana@redhat.com>
Cc: Steve Winslow <swinslow@linuxfoundation.org>, linux-spdx@vger.kernel.org
Subject: Re: [COX patch 1/2] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 100
Date: Thu, 6 Jun 2019 17:14:33 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1906061712430.2114@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAC1cPGyZO0CoDDEkd1+1BnMBEGE9HMYMSQVmdoGAETNiA21zoA@mail.gmail.com>

Richard,

On Thu, 6 Jun 2019, Richard Fontana wrote:

> On Thu, Jun 6, 2019 at 8:39 AM Steve Winslow
> <swinslow@linuxfoundation.org> 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.
> 
> I agree that the "Neither ... " paragraph should be kept in (I don't
> have an opinion on whether wrapping it in such a block is preferable).

The delimiter wrapping is useful in two aspects:

  1) It's simpler for tools

  2) It's trivial to grep for custom disclaimers without having knowledge
     of potential keywords.

Thanks,

	tglx

  reply	other threads:[~2019-06-06 15:14 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 [this message]
2019-06-08 20:50     ` Allison Randal
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:
  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=alpine.DEB.2.21.1906061712430.2114@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-spdx@vger.kernel.org \
    --cc=rfontana@redhat.com \
    --cc=swinslow@linuxfoundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).