From: Jeff King <peff@peff.net>
To: "Joshua J. Kugler" <joshua@azariah.com>
Cc: git@vger.kernel.org
Subject: Re: includeIf appears to not be working
Date: Mon, 12 Dec 2022 15:57:21 -0500 [thread overview]
Message-ID: <Y5eVsb8rIH9TFgIj@coredump.intra.peff.net> (raw)
In-Reply-To: <Y5eVTrK2CO0h5BPl@coredump.intra.peff.net>
On Mon, Dec 12, 2022 at 03:55:42PM -0500, Jeff King wrote:
> > Is there a debug command which can show if the gitdir is/isn't
> > matching like I thought it should? What other command output could
> > help debug this?
>
> No, there's no debug/tracing code for this feature. You'd have to run it
> under gdb (break on the include_by_gitdir function).
Oh, one other command you could try:
git rev-parse --absolute-git-dir
while in the repository in question. I think that would do the same
normalization of the path (including resolving symlinks). So that would
tell you what Git should be matching against.
-Peff
prev parent reply other threads:[~2022-12-12 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:19 includeIf appears to not be working Joshua J. Kugler
2022-12-12 20:54 ` Eric Sunshine
2022-12-12 21:05 ` Joshua J. Kugler
2022-12-12 20:55 ` Jeff King
2022-12-12 20:57 ` Jeff King [this message]
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=Y5eVsb8rIH9TFgIj@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=joshua@azariah.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