| commit | 41f98fae0224c2d7043376a9c421b4e0e73cdd82 | |
| author | Jeff King <peff@peff.net> | |
| Thu, 7 Dec 2023 07:24:04 +0000 (7 02:24 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 8 Dec 2023 23:26:21 +0000 (9 08:26 +0900) | ||
| tree | 6d8efe76210cfb9dc176146b548acf7008990f64 | treesnapshot (tar.gz zip) |
| parent | d49cb162fa752d62cf20548ae057471d348e42ae | commitdiff |
config: reject bogus values for core.checkstat
If you feed nonsense config like:
git -c core.checkstat=foobar status
we'll silently ignore the unknown value, rather than reporting an error.
This goes all the way back to c08e4d5b5c (Enable minimal stat checking,
2013-01-22).
Detecting and complaining now is technically a backwards-incompatible
change, but I don't think anybody has any reason to use an invalid value
here. There are no historical values we'd want to allow for backwards
compatibility or anything like that. We are better off loudly telling
the user that their config may not be doing what they expect.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If you feed nonsense config like:
git -c core.checkstat=foobar status
we'll silently ignore the unknown value, rather than reporting an error.
This goes all the way back to c08e4d5b5c (Enable minimal stat checking,
2013-01-22).
Detecting and complaining now is technically a backwards-incompatible
change, but I don't think anybody has any reason to use an invalid value
here. There are no historical values we'd want to allow for backwards
compatibility or anything like that. We are better off loudly telling
the user that their config may not be doing what they expect.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| config.c | diffblobblamehistory |