From: Martin Jansa <martin.jansa@gmail.com>
To: Yao Xinpan <yaoxp@cn.fujitsu.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH] add license file: DMTF
Date: Mon, 9 Jun 2014 10:30:44 +0200 [thread overview]
Message-ID: <20140609083044.GC7549@jama> (raw)
In-Reply-To: <1402288294-19549-1-git-send-email-yaoxp@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 3358 bytes --]
On Mon, Jun 09, 2014 at 12:31:34PM +0800, Yao Xinpan wrote:
> hi all
> I want to add software which associates with DMTF into rootfs.
> There is WARNING as follows when build:
> "WARNING: cim-schema: No generic license file exists for: DMTF in any provider"
>
> Could add license DMTF into yocto?
into oe-core? You can have license files in your own layer, do you plan
to add the recipe for "software which associates with DMTF" to oe-core?
Regards,
> Signed-off-by: Yao Xinpan <yaoxp@cn.fujitsu.com>
> ---
> meta/files/common-licenses/DMTF | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 meta/files/common-licenses/DMTF
>
> diff --git a/meta/files/common-licenses/DMTF b/meta/files/common-licenses/DMTF
> new file mode 100644
> index 0000000..54a2812
> --- /dev/null
> +++ b/meta/files/common-licenses/DMTF
> @@ -0,0 +1,34 @@
> +// Copyright 1998-2008 Distributed Management Task Force, Inc. (DMTF).
> +// All rights reserved.
> +// DMTF is a not-for-profit association of industry members dedicated
> +// to promoting enterprise and systems management and interoperability.
> +// DMTF specifications and documents may be reproduced by
> +// members and non-members, provided that correct attribution is given.
> +// As DMTF specifications may be revised from time to time,
> +// the particular version and release date should always be noted.
> +//
> +// Implementation of certain elements of this standard or proposed
> +// standard may be subject to third party patent rights, including
> +// provisional patent rights (herein "patent rights"). DMTF makes
> +// no representations to users of the standard as to the existence
> +// of such rights, and is not responsible to recognize, disclose, or
> +// identify any or all such third party patent right, owners or
> +// claimants, nor for any incomplete or inaccurate identification or
> +// disclosure of such rights, owners or claimants. DMTF shall have no
> +// liability to any party, in any manner or circumstance, under any
> +// legal theory whatsoever, for failure to recognize, disclose, or
> +// identify any such third party patent rights, or for such party's
> +// reliance on the standard or incorporation thereof in its product,
> +// protocols or testing procedures. DMTF shall have no liability to
> +// any party implementing such standard, whether such implementation
> +// is foreseeable or not, nor to any patent owner or claimant, and shall
> +// have no liability or responsibility for costs or losses incurred if
> +// a standard is withdrawn or modified after publication, and shall be
> +// indemnified and held harmless by any party implementing the
> +// standard from any and all claims of infringement by a patent owner
> +// for such implementations.
> +//
> +// For information about patents held by third-parties which have
> +// notified the DMTF that, in their opinion, such patent may relate to
> +// or impact implementations of DMTF standards, visit
> +// http://www.dmtf.org/about/policies/disclosures.php.
> --
> 1.8.4.2
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-06-09 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 4:31 [PATCH] add license file: DMTF Yao Xinpan
2014-06-09 8:30 ` Martin Jansa [this message]
2014-06-10 2:29 ` yaoxp
2014-06-10 7:07 ` Burton, Ross
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=20140609083044.GC7549@jama \
--to=martin.jansa@gmail.com \
--cc=yaoxp@cn.fujitsu.com \
--cc=yocto@yoctoproject.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 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.