archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <>
Subject: [COX patch 0/2] Deep review of 'COX' disclaimers
Date: Thu, 06 Jun 2019 11:53:26 +0200	[thread overview]
Message-ID: <> (raw)

The 'COX' disclaimers are named after the assumed inventor (Alan Cox). They
contain the following pattern:

    Neither $PERSON nor $CORP admit liability nor provide warranty for any
    of this software. This material is provided as is and at no charge.

$PERSON and $CORP are placeholders for individuals and corporations which
vary with the various source files. But other than the names the wording is
identical throughout all.

The individuals have a copyright notice in the affected files. The email
address belongs to the associated corporates.

Interesting question what to do with those.



             reply	other threads:[~2019-06-06 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  9:53 Thomas Gleixner [this message]
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
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 0/2] Deep review of '\''COX'\'' disclaimers' \

* 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
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).