Re: [PATCH 3/3] safe.directory: document and check that it's ignored in the environment
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 9, 2022, 21:45 UTC
- Message-ID
- <xmqqlevabcsu.fsf@gitster.g>
- In-Reply-To
- <20220509213915.GA2043@szeder.dev>
SZEDER Gábor <szeder.dev@gmail.com> writes:
Show 5 quoted lines
> repositoy could trivially safe-list itself. However, it's unclear (to > me) why 'git -c safe.directory=...' is ignored: 8959555cee > (setup_git_directory(): add an owner check for the top-level > directory, 2022-03-02) only states that it's ignored, but doesn't > justify why. Now, let's suppose that there was a compelling reason to
Correct. I do not think it is a restriction with any sensible justification, just that it happened to be implemented that way.
IOW, I am saying that GIT_SAFE_DIRECTORIES may be a lot nicer user interface than fixing the "we ignore 'git -c safe.directory'?" bug.