From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: Enhancements/Bugs closed WW11!
Date: Mon, 15 Mar 2021 12:14:00 -0700 [thread overview]
Message-ID: <072f01d719cf$5b6884a0$12398de0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
All,
The below were the owners of enhancements or bugs closed during the last
week!
Who
Count
randy.macleod@windriver.com
4
alexandre.belloni@bootlin.com
3
richard.purdie@linuxfoundation.org
3
ross@burtonini.com
1
kory.maincent@bootlin.com
1
bruce.ashfield@gmail.com
1
Grand Total
13
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: 8519 bytes --]
next reply other threads:[~2021-03-15 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:14 Stephen Jolley [this message]
2022-03-14 23:15 Enhancements/Bugs closed WW11! sjolley.yp.pm
2023-03-20 21:54 sjolley.yp.pm
2024-03-18 23:56 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='072f01d719cf$5b6884a0$12398de0$@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 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 NNTP newsgroup(s).