| commit | 35840a3e789dd67528caefc146deb698bd6ac7a5 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Tue, 27 Jan 2015 20:26:03 +0000 (27 12:26 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 2 Feb 2015 19:28:55 +0000 (2 11:28 -0800) | ||
| tree | c928cfb199de89df53cc5cbb8b017cd37b314dcc | treesnapshot (tar.gz zip) |
| parent | 502e7f9851768974a5b45a9dc00882231dac5c90 | commitdiff |
CodingGuidelines: describe naming rules for configuration variables
We may want to say something about command line option names in the
new section as well, but for now, let's make sure everybody is clear
on how to structure and name their configuration variables.
The text for the rules are partly taken from the log message of
Jonathan's 6b3020a2 (add: introduce add.ignoreerrors synonym for
add.ignore-errors, 2010-12-01).
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We may want to say something about command line option names in the
new section as well, but for now, let's make sure everybody is clear
on how to structure and name their configuration variables.
The text for the rules are partly taken from the log message of
Jonathan's 6b3020a2 (add: introduce add.ignoreerrors synonym for
add.ignore-errors, 2010-12-01).
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/CodingGuidelines | diffblobblamehistory |