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

Re: [PATCH 3/5] get_shallow_commits: Avoid memory leak if a commit has been reached already.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 25, 2006, 23:36 UTC
Message-ID
<Pine.LNX.4.63.0611260033410.30004@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7v1wnr2twq.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sat, 25 Nov 2006, Junio C Hamano wrote:
> I think you could pretend the commit->util field to be of some kind of 
> int and avoid the allocation altogether ;-).

I actually thought about that, and found it too dangerous. But of course, since we need at least a 32-bit architecture, chances are very high that a pointer is castable to an int.

Ciao, Dscho

Previous: Junio C Hamano
Message 5 of 5 in “get_shallow_commits: Avoid memory leak if a commit has been reached already.”
  1. 3/5 get_shallow_commits: Avoid memory leak if a commit has been reached already.Alexandre Julliard, Nov 24, 2006
  2. Anand KumriaNov 25, 2006
  3. Johannes SchindelinNov 25, 2006
  4. Junio C HamanoNov 25, 2006
  5. Johannes SchindelinNov 25, 2006

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.