summaryrefslogtreecommitdiff
path: root/GIT-VERSION-GEN
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-12-01 18:36:15 (GMT)
committerJunio C Hamano <gitster@pobox.com>2010-12-01 21:40:12 (GMT)
commit6b3020a241e2c0a1eaa6b74a10a796603bb90975 (patch)
treeb9c275f975e2a1dbb39f2e5ef326afee51dd7a90 /GIT-VERSION-GEN
parent593ce2bea5dad436e87b5dd37c205961d73feae9 (diff)
downloadgit-6b3020a241e2c0a1eaa6b74a10a796603bb90975.zip
git-6b3020a241e2c0a1eaa6b74a10a796603bb90975.tar.gz
git-6b3020a241e2c0a1eaa6b74a10a796603bb90975.tar.bz2
add: introduce add.ignoreerrors synonym for add.ignore-errors
The "[add] ignore-errors" tweakable introduced by v1.5.6-rc0~30^2 (Add a config option to ignore errors for git-add, 2008-05-12) does not follow the usual convention for naming values in the git configuration file. What convention? Glad you asked. The section name indicates the affected subsystem. The subsection name, if any, indicates which of an unbound set of things to set the value for. The variable name describes the effect of tweaking this knob. The section and variable names can be broken into words using bumpyCaps in documentation as a hint to the reader. These word breaks are not significant at the level of code, since the section and variable names are not case sensitive. The name "add.ignore-errors" includes a dash, meaning a naive configuration file like [add] ignoreErrors does not have any effect. Avoid such confusion by renaming to the more consistent add.ignoreErrors, but keep the old version for backwards compatibility. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Acked-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'GIT-VERSION-GEN')
0 files changed, 0 insertions, 0 deletions