From: Andrew Cagney <ac131313@cygnus.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: next gettextization step
Date: Mon, 24 Jun 2002 19:29:00 -0000 [thread overview]
Message-ID: <3D17D59A.1000308@cygnus.com> (raw)
In-Reply-To: <877kkqq6y8.fsf@fleche.redhat.com>
> Index: ChangeLog
> from Tom Tromey <tromey@redhat.com>
>
> * main.c: Marked all strings with _().
> * configure: Rebuilt.
> * configure.in (PACKAGE): New subst.
> (AC_OUTPUT): Create po/Makefile.in and po/Makefile.
> (SUBDIRS): Added po.
> * po/gdb.pot: New file.
> * po/POTFILES.in: New file.
> * po/.cvsignore: New file.
> * po/Make-in: New file.
>
Tom,
If I understand things correctly, the main.c change can go in without
the po/ change? The configure.in patch can also be split in two leaving
out the po/ part?
If this is correct then those parts are free to go in.
I'd like to see the po/ directory issues resolved (I've sent an e-mail
to binutils) before that is also created.
enjoy,
Andrew
PS: Every single printf_filtered() will need the change. printf() and
fprintfs() however should be considered illegal - they need to be
changed to printf_filtered()s.
next prev parent reply other threads:[~2002-06-25 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 9:32 Tom Tromey
2002-06-23 9:47 ` Tom Tromey
2002-06-24 10:05 ` Andrew Cagney
2002-06-24 13:58 ` Tom Tromey
2002-06-24 16:33 ` Andrew Cagney
[not found] ` <mailpost.1024961614.24442@news-sj1-1>
2002-06-24 16:37 ` cgd
2002-06-24 16:51 ` Tom Tromey
2002-06-24 19:24 ` Andrew Cagney
2002-06-24 20:10 ` Tom Tromey
2002-06-25 1:26 ` Andreas Schwab
2002-06-24 19:29 ` Andrew Cagney [this message]
2002-06-24 22:32 ` Tom Tromey
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=3D17D59A.1000308@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.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