From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Cohen, Eugene" <eugene@hp.com>,
"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: .clang-format for edk2
Date: Mon, 1 May 2017 17:16:26 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F57D16F93B@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <AT5PR84MB0291C02719DEAB8181ED40BEB4130@AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM>
Eugene,
I am not aware of any efforts. Though this looks very interesting.
There was a previous email thread on use of Astyle to get close to
the style from the EDK II C Coding Standards Specification.
https://lists.01.org/pipermail/edk2-devel/2017-March/008914.html
Best regards,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Cohen, Eugene
> Sent: Friday, April 28, 2017 9:07 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org <edk2-
> devel@ml01.01.org>
> Subject: [edk2] .clang-format for edk2
>
> It looks like the ".clang-format" syntax it being adopted by the majority of editors
> (including Visual Studio and Visual Studio Code).
>
> Do you know of any effort to map the edk2 coding convention into a .clang-format file
> that can be committed to edk2 eventually?
>
> Thanks,
>
> Eugene
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-05-01 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:07 .clang-format for edk2 Cohen, Eugene
2017-05-01 17:16 ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F57D16F93B@ORSMSX113.amr.corp.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