[PATCH v2 2/4] ll-merge.c: refactor `read_merge_config()` to use `git_config_string()`

There is one slight behavior change, previously merge.default silently ignored a NULL value and didn't raise any error. But, in the same function, all other values raise an error on a NULL value. So to conform with other call sites in Git, a NULL value for merge.default raises an error.

Re: [PATCH v2 2/4] ll-merge.c: refactor `read_merge_config()` to use `git_config_string()`

Tanay Abhra tanay...@gmail.com writes: There is one slight behavior change, previously merge.default silently ignored a NULL value and didn't raise any error. But, in the same function, all other values raise an error on a NULL value. So to conform with other call sites in Git, a NULL value

Re: [PATCH v2 2/4] ll-merge.c: refactor `read_merge_config()` to use `git_config_string()`

Tanay Abhra tanay...@gmail.com writes: There is one slight behavior change, previously merge.default silently ignored a NULL value and didn't raise any error. But, in the same function, all other values raise an error on a NULL value. So to conform with other call sites in Git, a NULL value