Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-oe krogoth release
Date: Thu, 05 May 2016 14:48:14 -0400	[thread overview]
Message-ID: <20160505184814.GI27602@denix.org> (raw)
In-Reply-To: <572B8B21.801@gmail.com>

On Thu, May 05, 2016 at 11:04:17AM -0700, akuster808 wrote:
> 
> 
> On 05/05/2016 10:28 AM, Denys Dmytriyenko wrote:
> > On Thu, May 05, 2016 at 01:19:32PM -0400, Denys Dmytriyenko wrote:
> >> Armin, et al,
> >>
> >> What's the deal with meta-oe branching into krogoth way too early (April 12th 
> >> pretty much) and missing on many updates and fixes that went in to master last 
> >> couple of weeks (delayed due to Martin's well deserved absence at the time) 
> >> before the actual release of OE-Core last Thursday? I was hoping there would 
> >> be a global merge/rebase from master to krogoth at the time of release, but it 
> >> doesn't seem to be the case. It would be a shame if those were missed from 
> >> krogoth... Are there any plans to pick them up?
> > 
> > BTW, I do see your past pull request "attempts" (May 2, April 28) on the list, 
> > but they don't seem to be pushed. I guess I should re-phrase my question - do 
> > you plan to push the latest pull request and what is the ETA? Thanks!
> 
> That is up to Martin. I don't have write access.

Oops, didn't know that. That would explain the delay then. Sorry for the noise.

-- 
Denys


  reply	other threads:[~2016-05-05 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 17:19 meta-oe krogoth release Denys Dmytriyenko
2016-05-05 17:28 ` Denys Dmytriyenko
2016-05-05 18:04   ` akuster808
2016-05-05 18:48     ` Denys Dmytriyenko [this message]
2016-05-05 18:25   ` Martin Jansa
2016-05-05 18:48     ` Denys Dmytriyenko
2016-05-06  1:05       ` Denys Dmytriyenko

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=20160505184814.GI27602@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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