From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW22
Date: Mon, 1 Jun 2020 09:54:01 -0700 [thread overview]
Message-ID: <11ec01d63835$407f1220$c17d3660$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW22 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=8805> 8805
Detect and warn people naming functions something_remove_something
richard.purdie@linuxfoundation.org
unassigned@yoctoproject.org
3.99
3.2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=10061> 10061
Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing
nicely
richard.purdie@linuxfoundation.org
unassigned@yoctoproject.org
3.99
3.2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=10096> 10096
Allow PREFERRED_VERSION miss to be fatal
richard.purdie@linuxfoundation.org
unassigned@yoctoproject.org
3.99
3.2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13905> 13905
[QA 3.0.3 RC2] failure in ptest: strace.printstrn-umoven.gen and
strace.printpath-umovestr.gen
randy.macleod@windriver.com
anuj.mittal@intel.com
3.0.3
3.0.4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13906> 13906
[QA 3.0.3 RC2] failure in ptest: valgrind.helgrind/tests/tc19_shadowmem
randy.macleod@windriver.com
anuj.mittal@intel.com
3.0.3
3.0.4
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 17025 bytes --]
next reply other threads:[~2020-06-01 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 16:54 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-31 23:51 M+ & H bugs with Milestone Movements WW22 Stephen Jolley
2022-05-30 23:06 sjolley.yp.pm
2023-06-06 3:27 sjolley.yp.pm
2025-06-03 4:48 Stephen K Jolley
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='11ec01d63835$407f1220$c17d3660$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=yocto@yoctoproject.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.