Laszlo, I support your idea of having a meaningful description for BZ, for commit message, for code comments.
Thinking from 1 or 2 years from now, the simple message we created may help nothing to remind me or others why the changes were made. We cannot reply on people's memories and even the people that have the memories may left the community. So, documentation is necessary. But I remember that our development process document in WIKI doesn't require anything on the commit message perspective. IMO, at least the commit message should contain: * current status or reason(fail, lack of a feature, bad coding style) * impact of the change or result (fail to pass, feature enabled, coding style improved) Can someone help to emphasize the requirement in the WIKI? Thanks, Ray -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#65398): https://edk2.groups.io/g/devel/message/65398 Mute This Topic: https://groups.io/mt/76902353/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
