From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: openbmc@lists.ozlabs.org
Subject: interest in a minimal image recipe
Date: Tue, 15 Sep 2020 16:28:32 -0400 [thread overview]
Message-ID: <20200915202832.rq3os62pdj7mzaco@thinkpad.fuzziesquirrel.com> (raw)
I've heard a handful of times that meta-phosphor users often have to
remove the latest feature added by default to obmc-phosphor-image.
I have an RFC for an empty image that these users could bbappend and
opt-in to specific image features instead of having to repeatedly
opt-out.
If you like the opt-in approach, please drop a +1 and/or review my patch:
https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/36516
I bring this up now because I, and others have been adding new image
features to obmc-phosphor-image (e.g. turned on by default), and I would
like to start a discussion about what it means for an application to be
in the OpenBMC github organization. I would propose that it means it is
enabled and turned on by default in obmc-phosphor-image.
Looking forward to your thoughts.
-brad
next reply other threads:[~2020-09-15 20:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:28 Brad Bishop [this message]
2020-09-15 20:58 ` interest in a minimal image recipe Khetan, Sharad
2020-09-15 21:27 ` Sriram Ramkrishna
2020-09-17 20:10 ` Brad Bishop
2020-09-17 21:02 ` Ed Tanous
2020-09-21 13:21 ` Andrew Geissler
2020-09-17 20:56 ` Ed Tanous
2020-09-17 22:21 ` Khetan, Sharad
2020-09-21 15:05 ` Ed Tanous
2020-09-21 15:05 ` Ed Tanous
2020-09-22 2:03 ` Khetan, Sharad
2020-09-22 2:03 ` Khetan, Sharad
2020-09-22 16:54 ` Nancy Yuen
2020-09-21 12:55 ` Brad Bishop
2020-09-21 15:53 ` Ed Tanous
2020-09-21 17:52 ` Brad Bishop
2020-09-21 18:25 ` Ed Tanous
2020-09-21 19:08 ` Brad Bishop
2020-09-22 20:40 ` Vijay Khemka
2020-09-23 19:46 ` Ed Tanous
2020-09-23 19:49 ` Vijay Khemka
2020-09-21 18:20 ` Brad Bishop
2020-09-21 18:49 ` Ed Tanous
2020-09-21 19:01 ` Brad Bishop
2020-09-22 19:52 ` Vijay Khemka
2020-09-23 17:50 ` Brad Bishop
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=20200915202832.rq3os62pdj7mzaco@thinkpad.fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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.