From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW31
Date: Mon, 1 Aug 2022 14:44:13 -0700 [thread overview]
Message-ID: <0dc201d8a5ef$d8fd8610$8af89230$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW31 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14800> 14800
AB-INT PTEST: libgcrypt ptest intermittent failure
randy.macleod@windriver.com
ross.burton@arm.com
4.1
4.1 M3
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: 7920 bytes --]
next reply other threads:[~2022-08-01 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 21:44 sjolley.yp.pm [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 3:31 M+ & H bugs with Milestone Movements WW31 Stephen K Jolley
2023-08-07 19:30 Stephen K Jolley
2020-08-04 0:16 Stephen 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='0dc201d8a5ef$d8fd8610$8af89230$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox