From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] util-linux: Update License Information (remove GPLv3 Licnese)
Date: Sun, 17 Mar 2013 09:16:42 +0000 [thread overview]
Message-ID: <1363511802.6710.16.camel@ted> (raw)
In-Reply-To: <FC0195A5-8F7D-4750-95F6-53CEACBDEB31@gmail.com>
On Sat, 2013-03-16 at 22:03 -0700, Khem Raj wrote:
> On Mar 15, 2013, at 12:54 PM, Saul Wold <sgw@linux.intel.com> wrote:
>
> > The upstream authors have updated the licenses of a couple subcomponents,
> > these were GPLv3, but updated to be either GPLv2 or LGPLv2.1 accordingly.
> > These changes make the util-linux package become completely non-GPLv3.
>
> Is it possible to demote license from V3 to V2 like that I wonder
The maintainer sought out approval from the copyright holders so yes.
The more people who've changed the files in question, the harder it
becomes.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-17 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:54 [PATCH] util-linux: Update License Information (remove GPLv3 Licnese) Saul Wold
2013-03-17 5:03 ` Khem Raj
2013-03-17 9:16 ` Richard Purdie [this message]
2013-03-17 20:03 ` Khem Raj
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=1363511802.6710.16.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.