public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Yannik Tausch <dev@ytausch.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org,
	Manuel Lerchner <manuel.lerchner@quantco.com>,
	Yannik Tausch <yannik.tausch@quantco.com>
Subject: Re: [PATCH v2] merge-file: honor merge.conflictStyle outside of a repository
Date: Mon, 9 Feb 2026 10:08:24 +0100	[thread overview]
Message-ID: <aYmkCLbhZPPjKqNK@pks.im> (raw)
In-Reply-To: <3488DCC3-D127-465B-BB95-3D87BB2E48F6@ytausch.de>

On Sat, Feb 07, 2026 at 10:37:48PM +0100, Yannik Tausch wrote:
> diff --git a/builtin/merge-file.c b/builtin/merge-file.c
> index 46775d0c79..f9de636884 100644
> --- a/builtin/merge-file.c
> +++ b/builtin/merge-file.c
> @@ -95,12 +95,10 @@ int cmd_merge_file(int argc,
>  	xmp.style = 0;
>  	xmp.favor = 0;
>  
> -	if (startup_info->have_repository) {
> -		/* Read the configuration file */
> -		repo_config(the_repository, git_xmerge_config, NULL);
> -		if (0 <= git_xmerge_style)
> -			xmp.style = git_xmerge_style;
> -	}
> +	/* Read the configuration file */
> +	repo_config(repo, git_xmerge_config, NULL);
> +	if (0 <= git_xmerge_style)
> +		xmp.style = git_xmerge_style;
>  
>  	argc = parse_options(argc, argv, prefix, options, merge_file_usage, 0);
>  	if (argc != 3)

Makes sense. I was briefly wondering about error handling in the old/new
code, but unknown keys are already handled by `git_xmerge_config()`, and
we'd die in case we see one.

So this patch looks good to me overall, thanks!

Patrick

  parent reply	other threads:[~2026-02-09  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 15:06 [DOC] merge-file: document that merge.conflictStyle requires a repository Yannik Tausch
2026-02-05 19:11 ` Junio C Hamano
2026-02-05 20:27   ` [PATCH] merge-file: honor merge.conflictStyle outside of " Yannik Tausch
2026-02-05 20:44     ` Junio C Hamano
2026-02-05 20:51     ` Kristoffer Haugsbakk
2026-02-05 21:55       ` [PATCH v2] " Yannik Tausch
2026-02-06 21:53         ` Junio C Hamano
2026-02-07 21:28           ` Yannik Tausch
2026-02-07 21:37             ` Yannik Tausch
2026-02-07 21:47               ` Kristoffer Haugsbakk
2026-02-09  9:08               ` Patrick Steinhardt [this message]
2026-02-09 16:13                 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aYmkCLbhZPPjKqNK@pks.im \
    --to=ps@pks.im \
    --cc=dev@ytausch.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=manuel.lerchner@quantco.com \
    --cc=yannik.tausch@quantco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox