Re: Re: [PATCH v11 2/2] am: support --empty=<option> to handle empty patches

From: Aleen 徐沛文 <pwxu@coremail.cn>
Date: Nov 29, 2021, 10:00 UTC
Message-ID: <7cffa143.3af.17d6b2371c7.Coremail.pwxu@coremail.cn>
In-Reply-To: <36706841.2ec.17d6afdb326.Coremail.pwxu@coremail.cn>

It is quite complicated to support 'git commit --allow-empty' extracting messages from an empty patch, because 'git am' has to find somewhere to store the parsed state for 'git commit' to read. How about directly supporting another interactive option '--allow-empty' for 'git am' to keep recording?

Show 12 quoted lines

> Dears Hamano,
> 
>    Elijah Newren has given two better suggestions:
> 
>        1. Use 'ask' rather than 'die'
>        2. When erroring out 'Patch is empty', print out a tutorial information
>           to help users using 'git commit --allow-empty' to keep recording as 
>           an empty commit.
> 
>    Should we continue to implement these features in current PR?
> 
> Aleen

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