From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: [PATCH 003/160] gettext: fix bug in git-sh-i18n's eval_gettext() by using envsubst(1)
Date: Sun, 14 Nov 2010 23:26:25 +0100 [thread overview]
Message-ID: <AANLkTik4ds++er=MpLOZZ9DbhADbBrckyW3u0ydxbiv+@mail.gmail.com> (raw)
In-Reply-To: <20101114214731.GA16413@burratino>
On Sun, Nov 14, 2010 at 22:47, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Yes, that is what $gmane/160842 is about (also see $gmane/137738 for
> background). In this case, a simple local stub xmalloc/xrealloc etc
> to take care of checking for NULL seems fine, indeed.
Indeed. The problem is that even if I did that I couldn't convince the
Makefile in cooperating with creating my binary in a special
way. That's what I needed help with.
Then again I'm not a Makefile wiz and only tried to poke it for 20
minutes or so. So I might be missing something obvious.
next prev parent reply other threads:[~2010-11-14 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 15:07 [PATCH 000/160] [PULL] ab/i18n rebased on ab/i18n-prereqs Ævar Arnfjörð Bjarmason
2010-11-14 15:07 ` [PATCH 002/160] Makefile: Set NO_GETTEXT=YesPlease on Windows & MinGW Ævar Arnfjörð Bjarmason
2010-11-15 10:35 ` Erik Faye-Lund
2010-11-14 15:07 ` [PATCH 003/160] gettext: fix bug in git-sh-i18n's eval_gettext() by using envsubst(1) Ævar Arnfjörð Bjarmason
2010-11-14 18:16 ` Jonathan Nieder
2010-11-14 19:15 ` Junio C Hamano
2010-11-14 21:25 ` Ævar Arnfjörð Bjarmason
2010-11-14 21:27 ` Jonathan Nieder
2010-11-14 21:42 ` Ævar Arnfjörð Bjarmason
2010-11-14 21:47 ` Jonathan Nieder
2010-11-14 22:26 ` Ævar Arnfjörð Bjarmason [this message]
2010-11-16 0:53 ` [PATCH 000/160] [PULL] ab/i18n rebased on ab/i18n-prereqs Ævar Arnfjörð Bjarmason
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='AANLkTik4ds++er=MpLOZZ9DbhADbBrckyW3u0ydxbiv+@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jrnieder@gmail.com \
/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).