Re: [PATCH/RFC 0/5] add "unset.variable" for unsetting previously set variables

From: Jakub Narębski <jnareb@gmail.com>
Date: Oct 7, 2014, 11:17 UTC
Message-ID: <5433CBC3.5010202@gmail.com>
In-Reply-To: <xmqqvbo2meg5.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:

>   - "[config] safe = section.variable" will list variables that can
>     be included with the config.safeInclude mechanism.  Any variable
>     that is not marked as config.safe that appears in the file
>     included by the config.safeInclude mechanism will be ignored.

Why user must know which variables are safe, why it cannot be left to Git to know which configuration variables can call external scripts?

-- 
Jakub Narębski

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.