From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] db: Upgrade to 6.0.35
Date: Wed, 28 Sep 2016 18:44:27 +0300 [thread overview]
Message-ID: <cb1b590b-1ed5-f8bd-5083-a87bcfca003f@linux.intel.com> (raw)
In-Reply-To: <596619b6-5742-3284-0966-9ae0c9a7c5a3@windriver.com>
On 09/28/2016 06:44 PM, Mark Hatle wrote:
> On 9/28/16 10:26 AM, Khem Raj wrote:
>> We need to understand that disclaimer may be its requiring every one who is
>> distributing it to accept it.
>
> It is purely Oracle wanting to stop people from automatically downloading from
> them, also so they can harvest sales contacts. (nothing wrong with that, but it
> means that we should likely pick a different 'upstream'...)
>
> As Anibal indicated, the license itself has not changed -- so that is not an issue.
Mark, what is the current situation with 6.1/6.2 series of db? Are those
fit for updating to?
Alex
next prev parent reply other threads:[~2016-09-28 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 23:43 [PATCH] db: Upgrade to 6.0.35 Aníbal Limón
2016-09-27 23:44 ` Aníbal Limón
2016-09-28 1:24 ` Khem Raj
2016-09-28 15:04 ` Aníbal Limón
2016-09-28 15:26 ` Khem Raj
2016-09-28 15:35 ` Aníbal Limón
2016-09-28 15:44 ` Mark Hatle
2016-09-28 15:44 ` Alexander Kanavin [this message]
2016-09-28 16:19 ` Mark Hatle
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=cb1b590b-1ed5-f8bd-5083-a87bcfca003f@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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