From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] build-sys: use gettext 0.18.3 if possible
Date: Tue, 10 Jun 2014 14:04:42 +0200 [thread overview]
Message-ID: <201406101404.42618.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20140610115208.GG30975@x2.net.home>
On Tuesday 10 June 2014, Karel Zak wrote:
> On Tue, Jun 10, 2014 at 12:08:51PM +0200, Ruediger Meier wrote:
> > We add a little hack for backward compatibility on systems with
> > older gettext installed
> >
> > See 0576dbd3 and 81ed13ed.
> >
> > Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
> > ---
> > autogen.sh | 31 ++++++++++++++++++++++++++++++-
> > configure.ac | 3 ++-
> > 2 files changed, 32 insertions(+), 2 deletions(-)
>
> Ah, I see, it seems like another pin for our gettext voodoo doll.
Hehe.
> Applied.
Ooops, in the cover letter I've mentioned that the new function would
probably need some more small portability/safety fixes before final
patch. Anyway I'll send them later.
One more thing. Since we have "0.18.3" now in configure.ac you should
take care to release it next time on a system where at least this
version is available. It wouldn't look nice if we ship files from
different version.
cu,
Rudi
next prev parent reply other threads:[~2014-06-10 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 10:08 [PATCH] next try to update gettext version Ruediger Meier
2014-06-10 10:08 ` [PATCH] build-sys: use gettext 0.18.3 if possible Ruediger Meier
2014-06-10 11:52 ` Karel Zak
2014-06-10 12:04 ` Ruediger Meier [this message]
2014-06-10 12:16 ` Karel Zak
2014-06-10 12:23 ` Karel Zak
2014-06-10 13:41 ` Ruediger Meier
2014-06-10 13:57 ` Pádraig Brady
2014-06-10 15:25 ` Ruediger Meier
2014-06-10 17:51 ` Ruediger Meier
[not found] ` <53974319.7040608@gmail.com>
2014-06-11 22:18 ` [PATCH] next try to update gettext version Ruediger Meier
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=201406101404.42618.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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