summaryrefslogtreecommitdiff
path: root/util/dtd_parser
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2021-02-02 16:27:57 -0800
committerPatrick Georgi <pgeorgi@google.com>2021-02-06 09:08:04 +0000
commitca935d1107ccc3ba77cc6915360f17f38e2f328d (patch)
tree831ae6bc35d7fa9a7a4cc94bb61dbf9fc89b7c88 /util/dtd_parser
parent6109c2cf83480ba12bacfad832a3e36efc397c6b (diff)
Documentation: Codify some guidelines for headers and chain-including
There has been some repeated discussion about how header includes should be formatted, specifically on the topic of chain-including. The coding style currently doesn't say anything about the topic but clearly people have some basic assumptions. This patch tries to codify some common ground rules that are supposed to reflect the existing practice. Signed-off-by: Julius Werner <jwerner@chromium.org> Change-Id: Ibbcde306a814f52b3a41b58c7a33bdd99b0187e0 Reviewed-on: https://review.coreboot.org/c/coreboot/+/50247 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-by: HAOUAS Elyes <ehaouas@noos.fr> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Diffstat (limited to 'util/dtd_parser')
0 files changed, 0 insertions, 0 deletions