All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [AUH] Upgrade status: 2020-07-15
Date: Thu, 16 Jul 2020 16:55:27 +0100	[thread overview]
Message-ID: <09ec097fc3cd3f5bb1ebbc7248cc52e56716fbfb.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8drAJ8fvTC_KPhQ3yZr7KN7iaB-616DnQHmf43TjCFmg@mail.gmail.com>

On Thu, 2020-07-16 at 16:31 +0200, Alexander Kanavin wrote:
> we have changed the AUH behavior so that it sends all upgrade patches
> not just to maintainers, but also to this mailing list. What this
> means is that if you are interested in an upgrade, and would like to
> contribute to Yocto, do not hesitate to take these patches, and send
> them to the mailing list according to instructions in the mails. Do
> not wait for 'official' maintainers to do it!

I did pull a chunk of the successful ones into master-next for
evaluation/testing.

I had to drop libhandy as it breaks epiphany:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1175

I needed a fix for mpfr in meta-mingw. Also, vulkan-headers breaks
gstreamer-plugins:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1173

There is another build running of -next as I send this...

Cheers,

Richard





  reply	other threads:[~2020-07-16 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 16:44 [AUH] Upgrade status: 2020-07-15 auh
2020-07-16 14:31 ` [OE-core] " Alexander Kanavin
2020-07-16 15:55   ` Richard Purdie [this message]
2020-07-17 10:15     ` Alexander Kanavin
2020-07-17 17:46       ` Richard Purdie

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=09ec097fc3cd3f5bb1ebbc7248cc52e56716fbfb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@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 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.