]> git.ipfire.org Git - thirdparty/git.git/commit - Documentation/CodingGuidelines
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a274e0a) | patch
CodingGuidelines: clarify multi-line brace style
authorJeff King <peff@peff.net>
Tue, 17 Jan 2017 20:05:04 +0000 (15:05 -0500)
committerJunio C Hamano <gitster@pobox.com>
Tue, 17 Jan 2017 22:32:47 +0000 (14:32 -0800)
commit1797dc51766576453c64fd422e25741ead9b2687
treebb7a147714d15fed057f5e6c13ee26fdb15b97aatree | snapshot
parenta274e0a036ea886a31f8b216564ab1b4a3142f6ccommit | diff
CodingGuidelines: clarify multi-line brace style

There are some "gray areas" around when to omit braces from
a conditional or loop body. Since that seems to have
resulted in some arguments, let's be a little more clear
about our preferred style.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/CodingGuidelines diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.