Re: [PATCH 5/5] apply: respect merge.conflictStyle in --3way
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 24, 2019, 01:20 UTC
- Message-ID
- <xmqqo8y7gcrq.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <56c31310db9358673af9905910e3332893d798de.1571832177.git.liu.denton@gmail.com>
Denton Liu <liu.denton@gmail.com> writes:
Show 12 quoted lines
> Before, when doing a 3-way merge, the merge.conflictStyle option was not > respected and the "merge" style was always used, even if "diff3" was > specified. > > Call git_xmerge_config() at the end of git_apply_config() so that the > merge.conflictStyle config is read. > > Signed-off-by: Denton Liu <liu.denton@gmail.com> > --- > apply.c | 2 +- > t/t4108-apply-threeway.sh | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-)
Interesting.
I do not recall why I did not add this when I introduced the "diff3" style. If it were because I knew other parts of "git apply" were not prepared to see the common ancestor hunk and using the "diff3" style would have triggered breakage in them, I would remember, so hopefully there is no subtle and hidden gotchas like it.
The implementation to trigger the "diff3" style conflict presentation obviously is correct ;-)
Thanks.
Show 6 quoted lines
> test_apply_with_3way success default true > -test_apply_with_3way failure 'merge.conflictStyle = diff3' 'test_config merge.conflictStyle diff3' > +test_apply_with_3way success 'merge.conflictStyle = diff3' 'test_config merge.conflictStyle diff3' > > test_expect_success 'apply with --3way with rerere enabled' ' > test_config rerere.enabled true &&