From: Denys Dmytriyenko <denis@denix.org>
To: akuster808 <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Bind update
Date: Thu, 29 Mar 2018 18:33:48 -0400 [thread overview]
Message-ID: <20180329223348.GJ2786@denix.org> (raw)
In-Reply-To: <d08f4cbf-7604-0115-61ca-a020fe2164fd@gmail.com>
On Wed, Mar 28, 2018 at 07:48:34AM -0700, akuster808 wrote:
>
>
> On 03/28/2018 04:15 AM, Burton, Ross wrote:
> > Hi Armin,
> >
> > Does this mean you are working on the upgrade, or should someone else start now?
> I think I did it. just need to find my work.
Did your dog eat your work? ;)
> - armin
> >
> > Ross
> >
> > On 24 March 2018 at 15:35, akuster808 <akuster808@gmail.com> wrote:
> >> Hello,
> >>
> >> While working on updating the current bind to the next patch level, I
> >> noticed our current version 9.10.6 will EOL June 2018. I know we are
> >> under feature freeze for the Sumo release.
> >>
> >> Could we make an exception and allow an update of bind to the ESV
> >> version 9.11.3 ?, it EOL's Dec 2021.
> >>
> >> regards,
> >>
> >> armin
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2018-03-29 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 15:35 Bind update akuster808
2018-03-26 9:20 ` Alexander Kanavin
2018-03-26 14:49 ` akuster808
2018-03-28 11:15 ` Burton, Ross
2018-03-28 14:48 ` akuster808
2018-03-29 22:33 ` Denys Dmytriyenko [this message]
2018-03-30 0:49 ` akuster808
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=20180329223348.GJ2786@denix.org \
--to=denis@denix.org \
--cc=akuster808@gmail.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