Guys, it is a bit tricky to prevent discussions in a call when someone brings up a topic, and I'm not sure that blocking that is useful. The meetings are open and particularly people commenting here have been invited to the calls. Please make use of that opportunity and join, if you think that you have a strong opinion.
In this case, I made the suggestion to look at what is located in each heater file and cone up with clear interfaces, rather than jumping into the next "let's make coreboot source more similar to go by removing headset file guards" discussion. On Thu, 23 May 2019, 16:43 Julius Werner, <jwer...@chromium.org> wrote: > > > * We should be more strict about how we define our blocks’ APIs. > > > > Ok, but.. I just don't understand this proposal? Can someone explain? > > I second this... this sounds like another code style > discussion/change. Can we please keep all code style discussions on > the mailing list? Or if there really needs to be a VC meeting for such > a discussion, can it be pre-announced so everyone interested can > participate? >
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
