Re: What's cooking in git.git (Nov 2021, #07; Mon, 29)

From: Aleen 徐沛文 <pwxu@coremail.cn>
Date: Dec 7, 2021, 01:58 UTC
Message-ID: <1f1d7b66.4a.17d929d357c.Coremail.pwxu@coremail.cn>
In-Reply-To: <xmqqa6hdb3sx.fsf@gitster.g>

> Adding an option that aborts and trashes the state directory is much
> worse than not having a choice other than drop and keep, which is in
> turn a bit worse than having a way to countermand an option that was
> given earlier on the command line.

Another option to countermand an option is only meaningful when it can be applied as a resume value but not in such a case, I think. "--empty=<option>" is only kept in each am session, and it seems we can't countermand the option after the session.

$ 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.