This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: RFA: next gettextization step
- From: Tom Tromey <tromey at redhat dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: Eli Zaretskii <eliz at is dot elta dot co dot il>, gdb-patches at sources dot redhat dot com
- Date: 24 Jun 2002 15:11:20 -0600
- Subject: Re: RFA: next gettextization step
- References: <877kkqq6y8.fsf@fleche.redhat.com> <3D175146.7060702@cygnus.com>
- Reply-to: tromey at redhat dot com
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> Anyway, looking in the opcodes directory, the CVS repository
Andrew> appears to contain the following generated files:
Andrew> opcodes.pot (aka gdb.pot)
Andrew> *.gmo
Andrew> I'm wondering if it would be better to handle these generated
Andrew> files the same wah as for LEX and YACC output - the
Andrew> release/snapshot process generates those files.
Actually, the gmo files aren't in the repository. They do end up in
the source tree though.
I don't know enough about how gdb releases are done to really comment
on this. Is there any documentation on the process?
Tom