From: Paul Eggert <eggert@cs.ucla.edu>
To: Reuben Thomas <rrt@sc3d.org>, bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: build-aux/po/Makefile.in.in needs updating
Date: Sat, 4 Feb 2023 18:26:40 -0800 [thread overview]
Message-ID: <05902195-8d7a-20e3-5d95-3211ce4cbc5e@cs.ucla.edu> (raw)
In-Reply-To: <CAOnWdoiLEdDgd8vSu_817nw3qQfO1+q-9XNxakj0oNM5h=5fhg@mail.gmail.com>
On 2023-02-04 15:37, Reuben Thomas wrote:
> Bruno pointed out to me that there's a bug fixed in the Makfile.in.in from
> gettext 0.20.2, which postdates the 0.20 version found in gnulib. (The bug
> is that the Makefile.in.in has prerequisites on suffix rules, which are
> ignored.)
In Gnulib I'd normally run 'config/srclist-update <config/srclist.txt'
to propagate stuff from other projects into Gnulib, but Bruno typically
does Gettext-related stuff by hand so srclist-update doesn't do that.
I took a quick look at the differences between bleeding-edge Gettext
Makefile.in.in and bleeding-edge Gnulib Makefile.in.in and decided that
Bruno was a better judge for this sort of thing....
next prev parent reply other threads:[~2023-02-05 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 23:37 build-aux/po/Makefile.in.in needs updating Reuben Thomas
2023-02-05 2:26 ` Paul Eggert [this message]
2023-02-05 16:24 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05902195-8d7a-20e3-5d95-3211ce4cbc5e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.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 read-only IMAP folder(s) and NNTP newsgroup(s).