From: stephano <stephano.cetola@linux.intel.com>
To: edk2-devel@lists.01.org
Subject: Re: Community Meeting Minutes #2
Date: Fri, 26 Oct 2018 14:44:01 +0100 [thread overview]
Message-ID: <49cfb283-8947-da67-c514-b5fec619eefe@linux.intel.com> (raw)
In-Reply-To: <829e38d9-c679-8b16-f8e7-06e953bc88f4@linux.intel.com>
On 10/26/2018 9:46 AM, stephano wrote> Standard C Types
> ----------------
> ...We should have a code standard in
> place to require the use of one or the other, but not both.
I should be more clear here. When editing code, one should follow the
pattern currently being used. E.g. If EDK2 types are used the developer
should not mix in standard C types.
If committing new code, like developing a new module, the developer
should pick one of the two and stick with it.
That is how I interpreted the discussion but please feel free to comment
here if I misunderstood.
prev parent reply other threads:[~2018-10-26 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 8:46 Community Meeting Minutes #2 stephano
2018-10-26 13:44 ` stephano [this message]
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-list 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=49cfb283-8947-da67-c514-b5fec619eefe@linux.intel.com \
--to=devel@edk2.groups.io \
/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