git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] commit: don't use-editor when allow-empty-message

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
May 27, 2013, 14:07 UTC
Message-ID
<CALkWK0nm71QAM1FSwuL4sK8JQXmaUtXegjsLMmYOK-1Aaro39A@mail.gmail.com>
In-Reply-To
<1369663431-2405-1-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra wrote:
>  builtin/commit.c | 2 ++
>  1 file changed, 2 insertions(+)

I just made this dependent on the order in which options are parsed. If --allow-empty-message is specified before -m "", it works. Otherwise, not.

Sorry about the stupidity.
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 4 of 7 in “Commit with an empty message broken since v1.8.2.1”
  1. Mislav MarohnićMay 25, 2013
  2. commit: don't start editor if empty message is given with -mRené Scharfe, May 25, 2013
  3. commit: don't use-editor when allow-empty-messageRamkumar Ramachandra, May 27, 2013
  4. Ramkumar RamachandraMay 27, 2013
  5. commit: don't use-editor when allow-empty-messageRamkumar Ramachandra, May 27, 2013
  6. Antoine PelisseMay 27, 2013
  7. Ramkumar RamachandraMay 27, 2013

Read the whole thread, see it on lore, or plain text.

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