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

Re: [PATCH] fix memory leak in parse_object when check_sha1_signature fails

From
Junio C Hamano <junkio@cox.net>
Date
May 25, 2007, 02:38 UTC
Message-ID
<7virahtyo9.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070525020939.GT28023@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 11 quoted lines
> Carlos Rica <jasampler@gmail.com> wrote:
>> When check_sha1_signature fails, program is not terminated:
>> it prints an error message and returns NULL, so the
>> buffer returned by read_sha1_file should be freed before.
> ...
>> 		if (check_sha1_signature(sha1, buffer, size, typename(type)) 
>> 		< 0) {
> ...
>
> gmail strikes again.  The above line is wrapped, which means your
> patch is whitespace damaged and won't apply properly.

That is only between your eyes, imagination and your MUA (hint: "format: flowed").

For applying after saving it in mbox it does not pose a problem, but it _does_ affect people who want to comment on the patch while in MUA.

Is there a way to turn that "format: flawed" off?
Previous: Shawn O. Pearce
Message 3 of 3 in “fix memory leak in parse_object when check_sha1_signature fails”
  1. fix memory leak in parse_object when check_sha1_signature failsCarlos Rica, May 25, 2007
  2. Shawn O. PearceMay 25, 2007
  3. Junio C HamanoMay 25, 2007

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.