Jonathan Nieder <jrnieder@xxxxxxxxx> writes:
> Jeff King wrote:
>
>> Yes, looks good to me. You could potentially drop the old one from the
>> config:
>> ...
>> which may be less confusing to new users (who might ask "is there a
>> difference between the two?").
>
> Right, I prefer to keep it documented for the old and forgetful users
> (who might ask "why does this configuration work?").
We actually need to stress the fact that _only_ newer git will understand
"add.ignoreErrors", so people with older git (especially the ones who need
to use both older and newer versions of git) may need to keep using the
older form in their configuration, no?
Perhaps phrasing it like this, and then issue v1.7.{0,1,2,3}.X maintenance
release to reduce the chance of inconveniencing the users?
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 1df0f65..5b6f667 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -539,9 +539,12 @@ core.sparseCheckout::
linkgit:git-read-tree[1] for more information.
add.ignore-errors::
+add.ignoreErrors::
Tells 'git add' to continue adding files when some files cannot be
added due to indexing errors. Equivalent to the '--ignore-errors'
- option of linkgit:git-add[1].
+ option of linkgit:git-add[1]. Older versions of git accept only
+ `add.ignore-errors`, whose name goes against the convention, so
+ newer versions of git honor `add.ignoreErrors` as well.
alias.*::
Command aliases for the linkgit:git[1] command wrapper - e.g.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html