From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 1/3] Don't save the commit buffer in git-describe.
Date: Wed, 10 Jan 2007 06:36:29 -0500 [thread overview]
Message-ID: <20070110113629.GA25251@spearce.org> (raw)
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
reply other threads:[~2007-01-10 11:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070110113629.GA25251@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.