RE: [PATCH 0/2] am: support --always option to am empty commits

From: Aleen <aleen42@vip.qq.com>
Date: Nov 12, 2021, 06:42 UTC
Message-ID: <tencent_EEC1D953A204CC69ED49D8471A89110F3605@qq.com>
In-Reply-To: <6da5e984-1dcf-4c55-976c-49ffb8d128bf@web.de>

Dears René,

> The symmetry is compelling, but "always" is quite generic.  I can see
> e.g. someone expecting "git am --always" to imply --keep-non-patch.

> git commit and cherry-pick have --allow-empty, which is (a bit) more
> specific.  That seems to me a better option name to copy for a commit-
> creating command like git am.

It was designed corresponding to --always option in git-format-patch, which will be pssed into git-diff-tree. As a commit-creating command, --allow-empty is apparently a better choice. I will re-submit it, thank you.

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