($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Stephen K Jolley <sjolley.yp.pm@gmail.com>
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW16
Date: Mon, 22 Apr 2024 22:14:36 -0700	[thread overview]
Message-ID: <CAK5yBb-4mN-MT4RdpEMs1Nb78YVNjw2kom38X_03BSxF5wDnrg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

All,

YP M+ or high bugs which moved to a new milestone in WW16 are listed below:
Priority Bug ID Short Description Changer Owner Was Became
Medium+ 6478 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=6478> Tweaks
to remove cruft from non-rootfs (container) images
randy.macleod@windriver.com newcomer@yoctoproject.org Future 5.99
14125 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14125> busybox
wget ssl is exposed to MitM attack due to CVE-2018-1000500
randy.macleod@windriver.com randy.macleod@windriver.com 5.0 M4 5.1 M1
15470 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=15470> Leading
space before } silently breaks parse randy.macleod@windriver.com
newcomer@yoctoproject.org 0.0.0 5.1 M1

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(    *Cell*:                (208) 244-4460

* *Email*:                 *s
<stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com <jolley.yp.pm@gmail.com>*

[-- Attachment #2: Type: text/html, Size: 9525 bytes --]

             reply	other threads:[~2024-04-23  5:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  5:14 Stephen K Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-24 20:59 M+ & H bugs with Milestone Movements WW16 sjolley.yp.pm
2022-04-18 20:02 sjolley.yp.pm
2021-04-20  0:59 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=CAK5yBb-4mN-MT4RdpEMs1Nb78YVNjw2kom38X_03BSxF5wDnrg@mail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).