From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [dora][PATCH_V3] mesa: double check for eglplatform.h
Date: Sat, 19 Apr 2014 14:44:06 +0100 [thread overview]
Message-ID: <1397915046.15843.207.camel@ted> (raw)
In-Reply-To: <CAP9ODKrJaQTkDeDgcvTBu9=dRLwLJo=d9mVxvOgx+PAw5iSLyw@mail.gmail.com>
On Fri, 2014-04-18 at 20:38 -0300, Otavio Salvador wrote:
> So WHAT is holding a bugfix for a regression to be merged? I am very
> disappointed with the maintenance in the Dora branch.
>
> 1. a change has been added without testing other layers hosted in YP.
> 2. it has been merged without being ran in YP AB.
> 3. I reported the issue in the same day it has been merged
> 4. it has been 10 days and this has not yet been reverted/fixed.
>
> So CAN THIS BE MERGED PLEASE?
WHY HAVE YOU NOT REPLIED TO BUG 6098? I ASKED YOU SOMETHING THERE 9
WHOLE DAYS AGO? IT IS A HIGH!!!! ITS BEEN OPEN 17 DAYS!!!!
I happen to know you've been travelling/busy and likely haven't had
time. Fair enough, it happens.
I have also been travelling, any spare cycles were directed to the 1.6
release and the beaglebone problem which was threatening to disrupt it.
Right now its a 4 day holiday weekend in the UK. I should be out trying
to relax, instead I'm horribly jetlagged and even better, reading all
caps emails from you.
This is to say nothing of being a bit distracted after dropping an 80kg
stone hearth on the end of one of my fingers a couple of weeks ago,
fracturing it, then reacting badly to some antibiotics to add to the
fun.
As it happens I merged the fix this morning before I read this, it was
already in the queue. I'd planned to do so sooner but hadn't got around
to it. Several of those days were looking into the regression and
figuring out a way which fixed it, and fixed the other bug report the
problem was solving.
In answer to your questions:
Its not policy to test every layer with a change in OE-Core. We do our
best to make sure things don't break. Not every change gets run through
the autobuilder. We do run things through the AB before a release
though. 1.5.2 has not been released yet and this issue will get resolved
before that happens.
I do wish we've been able to act sooner, equally most of the people
involved have various pressures on their time. We do our best.
Cheers,
Richard
next prev parent reply other threads:[~2014-04-19 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 14:51 [dora][PATCH_V3] mesa: double check for eglplatform.h Valentin Popa
2014-04-16 3:00 ` Robert Yang
2014-04-18 23:38 ` Otavio Salvador
2014-04-19 13:44 ` Richard Purdie [this message]
2014-04-19 14:24 ` Otavio Salvador
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=1397915046.15843.207.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.