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

Re: inaccurate commit message message?

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Sep 4, 2010, 23:07 UTC
Message-ID
<AANLkTi=eK4qt7KLg7z-3vqV+hgUoW_xire6WftBJAYku@mail.gmail.com>
In-Reply-To
<AANLkTi=Vb2cQHPo388m9HYVdYkk3XC_-pM9bm182PWyf@mail.gmail.com>
Heya,
On Sat, Sep 4, 2010 at 17:55, Ramana Kumar <ramana.kumar@gmail.com> wrote:
> The documentation, both in man git-commit and in the commit message
> message, is misleading when you do git commit --verbose.
Correct.
> My proposal is to make it less misleading, by saying in at least one,
> and ideally both, of those places what you just told me for the first
> time: when you do a git commit --verbose, the diff lines and
> everything after will be ignored for the commit message.

Sounds like a good idea. See builtin/commit.c around line 660. You'll want to check for the verbose flag and adjust the message printed there accordingly. See Documentation/SubmittingPatches.txt on how to submit patches.

Please do ask if you have any questions, I'd be glad to help.
-- 
Cheers,

Sverre Rabbelier
Previous: Ramana Kumar
Message 4 of 4 in “inaccurate commit message message?”
  1. Ramana KumarSep 4, 2010
  2. Sverre RabbelierSep 4, 2010
  3. Ramana KumarSep 4, 2010
  4. Sverre RabbelierSep 4, 2010

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.