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

Re: How to get the original raw commit message without removing extra leading/trailing line breaks

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 28, 2022, 05:53 UTC
Message-ID
<xmqq5yny62s1.fsf@gitster.g>
In-Reply-To
<1BEBB3E1-0089-44CD-8D3B-3AA424C90E48@pmease.com>
PMEase <robin@pmease.com> writes:
[jc: wrapped overly long lines]
Show 6 quoted lines
> I am using command "git show --format=raw <commit hash>" to get
> raw commit object in order to verify the GPG signature in my
> program to customize public key loading. However in the raw commit
> object, extra line breaks before and after the commit message is
> removed, which cause the signature verification failure as git
> generates the signature without removing those line breaks.

"git show --format=raw <commit object name>" will not give "raw commit object" to begin with. It indents the message by four spaces.

"git cat-file commit <commit object name>" is what you want, I think.

Previous: PMEaseNext: PMEase
Message 2 of 5 in “How to get the original raw commit message without removing extra leading/trailing line breaks”
  1. PMEaseMar 28, 2022
  2. Junio C HamanoMar 28, 2022
  3. PMEaseMar 28, 2022
  4. Junio C HamanoMar 28, 2022
  5. PMEaseMar 28, 2022

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.