From: Tian Yuchen <a3205153416@gmail.com>
To: Karthik Nayak <karthik.188@gmail.com>, git@vger.kernel.org
Cc: gitster@pobox.com
Subject: Re: [PATCH v5 2/2] setup: allow cwd/.git to be a symlink to a directory
Date: Wed, 18 Feb 2026 19:20:05 +0800 [thread overview]
Message-ID: <5db39190-da1b-4807-bc2e-2ce631d7815b@gmail.com> (raw)
In-Reply-To: <CAOLa=ZSAjDbC5bM+XvNwXW_WLWDiPfzAgaB+gHR6+DwhMW3uEw@mail.gmail.com>
Hi Karthik,
> But we don't really do this no? We were calling `read_gitfile_gently()`
> before and continue to do so, so there was no change regards to calling
> `stat()` here. Or am I missing something?
Oops, It seems I mixed up the changes in previous patches. I did make a
mistake.
> But now we'd die. Correct? Doesn't that change the expected flow?
Yes, this is a regression I missed. If 'die_on_error' is false,
encountering an error like 'READ_GITFILE_ERR_INVALID_FORMAT' should
return 'GIT_DIR_INVALID_GITFILE' rather than dying.
So in v6 I will ensure that we only delegate to
'read_gitfile_error_die()' when:
1. It is a happy case we want to ignore
2. It is a security case we MUST die on;
3. 'die_on_error' is tru
Otherwise, we should fall back to returning the error code as before.
Thank you for your time,
Regards,
Yuchen
>> + } else {
>> gitfile = xstrdup(dir->buf);
>> + }
>> /*
>> * Earlier, we tentatively added DEFAULT_GIT_DIR_ENVIRONMENT
>> * to check that directory for a repository.
>
> [snip]
next prev parent reply other threads:[~2026-02-18 11:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 18:21 [RFC] setup: fail if .git is not a file or directory Tian Yuchen
2026-02-11 19:47 ` Junio C Hamano
2026-02-12 17:33 ` Tian Yuchen
2026-02-12 17:24 ` [PATCH v2] " Tian Yuchen
2026-02-12 20:59 ` Junio C Hamano
2026-02-13 16:37 ` Tian Yuchen
2026-02-14 4:52 ` [PATCH v3] " Tian Yuchen
2026-02-15 8:41 ` Junio C Hamano
2026-02-15 16:22 ` Tian Yuchen
2026-02-16 2:37 ` Junio C Hamano
2026-02-16 16:02 ` Tian Yuchen
2026-02-17 8:41 ` [PATCH v4] setup: allow cwd/.git to be a symlink to a directory Tian Yuchen
2026-02-17 11:26 ` Karthik Nayak
2026-02-17 15:30 ` Tian Yuchen
2026-02-17 18:56 ` Karthik Nayak
2026-02-17 21:10 ` Junio C Hamano
2026-02-17 17:01 ` Junio C Hamano
2026-02-17 18:50 ` Karthik Nayak
2026-02-18 4:08 ` Tian Yuchen
2026-02-17 17:59 ` Karthik Nayak
2026-02-18 5:18 ` [PATCH v5 0/2] setup.c: v5 reroll Tian Yuchen
2026-02-18 5:18 ` [PATCH v5 1/2] setup: distingush ENOENT from other stat errors Tian Yuchen
2026-02-18 10:12 ` Karthik Nayak
2026-02-18 11:11 ` Tian Yuchen
2026-02-18 18:15 ` Junio C Hamano
2026-02-18 18:43 ` Junio C Hamano
2026-02-18 5:18 ` [PATCH v5 2/2] setup: allow cwd/.git to be a symlink to a directory Tian Yuchen
2026-02-18 10:27 ` Karthik Nayak
2026-02-18 11:20 ` Tian Yuchen [this message]
2026-02-18 18:25 ` Junio C Hamano
2026-02-19 5:11 ` Tian Yuchen
2026-02-15 17:08 ` [PATCH v3] setup: fail if .git is not a file or directory Tian Yuchen
2026-02-12 22:39 ` [RFC] " brian m. carlson
2026-02-12 22:45 ` Junio C Hamano
2026-02-12 23:03 ` brian m. carlson
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=5db39190-da1b-4807-bc2e-2ce631d7815b@gmail.com \
--to=a3205153416@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.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