From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Kristian Høgsberg" <krh@redhat.com>,
git@vger.kernel.org, "Paul Mackerras" <paulus@samba.org>
Subject: Re: [PATCH] Allow git_author|committer_info be called in the same expression
Date: Wed, 1 Aug 2007 11:35:45 +0200 [thread overview]
Message-ID: <81b0412b0708010235j3c731b38v32b5a717ae9f1f0b@mail.gmail.com> (raw)
In-Reply-To: <7vhcnj7gkt.fsf@assigned-by-dhcp.cox.net>
On 8/1/07, Junio C Hamano <gitster@pobox.com> wrote:
> "Alex Riesen" <raa.lkml@gmail.com> writes:
>
> > const char *git_committer_info(int error_on_no_name)
> > {
> > - return fmt_ident(getenv("GIT_COMMITTER_NAME"),
> > - getenv("GIT_COMMITTER_EMAIL"),
> > - getenv("GIT_COMMITTER_DATE"),
> > - error_on_no_name);
> > + static char *buffer;
> > + if (!buffer)
> > + buffer = xmalloc(FMT_IDENT_BUFSIZE);
>
> It is not like we are aiming to run on embedded devices, I think
Actually, I am planning to run it on Neo1973 (Openmoko),
which is quite embedded with its 128mb.
> trying to save static memory when the function is not called
> by doing things like this is not worth it. Why not just:
>
> static char buffer[FMT_IDENT_BUFSIZE];
>
> instead?
Just a custom. This is a big bugger, err... buffer.
> As to parts of the system that other people are primarily in
> charge of, git-gui 0.8.0 is already in as promised, updates to
> gitk were merged, and we've had a nice set of improvements from
BTW, gitk. Have you seen the gitk patches regarding errors in non-GIT
and not-yet-GIT directory?
prev parent reply other threads:[~2007-08-01 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 16:57 [PATCH] Allow git_author|committer_info be called in the same expression Alex Riesen
2007-08-01 9:24 ` Junio C Hamano
2007-08-01 9:35 ` Alex Riesen [this message]
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=81b0412b0708010235j3c731b38v32b5a717ae9f1f0b@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=krh@redhat.com \
--cc=paulus@samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).