git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Greg Hurrell <greg@hurrell.net>
Cc: git@vger.kernel.org
Subject: Re: git-checkout doesn't seem to respect config from include.path
Date: Wed, 2 Feb 2022 22:57:37 +0000	[thread overview]
Message-ID: <YfsMYTo1tND5JKNx@camp.crustytoothpaste.net> (raw)
In-Reply-To: <ee1dd453-e698-440a-911b-d14389e33715@beta.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

On 2022-02-02 at 16:04:26, Greg Hurrell wrote:
> However, when I try to run a command like `git checkout -b something`,
> Git dies with:
> 
>     fatal: unknown style 'zdiff3' given for 'merge.conflictstyle'
> 
> So, it looks like something in `git-checkout`'s option processing is
> causing it to disregard the override set via "include.path". In fact, it
> even disregards a value passed in with `-c` like this:
> 
>     git -c merge.conflictStyle=diff3 checkout -b something
> 
> Does this sound like a bug, or are my expectations off? I'd be happy to
> look into fixing this, but first would like to know whether it is
> expected behavior.

This definitely doesn't sound like the expected behavior here.  It's not
clear to me why this is happening, but it probably shouldn't be.  It
doesn't appear that we fail to call the config callback, since we've
been doing that since 2010.

What version of Git are you using that's not working?
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2022-02-02 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 16:04 git-checkout doesn't seem to respect config from include.path Greg Hurrell
2022-02-02 22:57 ` brian m. carlson [this message]
2022-02-03  7:48   ` Greg Hurrell
2022-02-03 15:54 ` Phillip Wood
2022-02-03 17:39   ` Greg Hurrell
2022-02-03 17:42     ` Greg Hurrell
2022-02-07 14:05     ` Phillip Wood
2022-02-03 18:07   ` Junio C Hamano
2022-02-07 14:01     ` Phillip Wood
2022-02-07 23:50       ` 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=YfsMYTo1tND5JKNx@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=greg@hurrell.net \
    /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;
as well as URLs for NNTP newsgroup(s).