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

[PATCH 1/3] Don't save the commit buffer in git-describe.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jan 10, 2007, 11:36 UTC
Message-ID
<20070110113629.GA25251@spearce.org>

The commit buffer (message of the commit) is not actually used by the git-describe process. We can save some memory by not keeping it around.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
 describe.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/describe.c b/describe.c
index f4029ee..3c2df03 100644
--- a/describe.c
+++ b/describe.c
@@ -162,6 +162,7 @@ int main(int argc, char **argv)
 	}
 
 	setup_git_directory();
+	save_commit_buffer = 0;
 
 	if (argc <= i)
 		describe("HEAD", 1);
-- 
1.4.4.4.gf027-dirty
Message 1 of 1 in “Don't save the commit buffer in git-describe.”
  1. 1/3 Don't save the commit buffer in git-describe.Shawn O. Pearce, Jan 10, 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.