Replies: 2 comments
-
|
Since I have in the past very strongly argued for the symbol modifications, I should probably give more feedback than just the upvote. I agree with Michael's reasoning and believe this would be an improvement to the process, better balancing auditing ability, actually using the in-flight code and finally migrating to it once adopted in a released specification. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This change has been pushed to the EDK II Code First Process. See the Source Code section. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
RFC: Modify Source Code Requirements in EDK II Code First Process
Revisions
Background
The EDK II Code First Process is described in this Tianocore wiki page.
In March 2025, the requirements were updated to align the process with the GitHub development model in this set of changes - edk2-devel - EDK II Code First Process Change.
As that change set notes, an open item was to remove the source code tagging requirement for names in source code that is currently described in EDK II Code First Process - Source Code:
Proposed Changes
[CODE_FIRST] <IssueId><IssueId>is a placeholder for the GitHub Code First issue for the change10000, the comment in C source code should be// [CODE_FIRST] 10000(1) is to:
(2) is to:
Every line is proposed to have a comment to:
Examples
DEC File
DSC File
PCD Assignment
New Component(s)
C Code
GUID Macro
Struct
Enum
Function Prototype
Modification in An Existing Function
Beta Was this translation helpful? Give feedback.
All reactions