public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dennis Bjorklund <db@zigo.dhs.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: other/2857: i18n, translations does not work
Date: Wed, 23 May 2001 00:16:00 -0000 [thread overview]
Message-ID: <20010523071603.29099.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR other/2857; it has been noted by GNATS.
From: Dennis Bjorklund <db@zigo.dhs.org>
To: Zack Weinberg <zackw@Stanford.EDU>
Cc: Mark Mitchell <mark@codesourcery.com>,
Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>,
<gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: Re: other/2857: i18n, translations does not work
Date: Wed, 23 May 2001 09:11:01 +0200 (CEST)
On Tue, 22 May 2001, Zack Weinberg wrote:
> A translation is something that could easily get added in a 3.0.x
> patch release
Definitely.
What about the pot file? I don't think it should be in cvs at all. It
should be automatically generated.
There is some files in POTFILES.in that does not exist. Maybe there are
also files that are not included in POTFILES.in.
Index: gcc/po/POTFILES.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/po/POTFILES.in,v
retrieving revision 1.44
diff -u -w -r1.44 POTFILES.in
--- POTFILES.in 2001/05/17 03:16:16 1.44
+++ POTFILES.in 2001/05/23 07:04:16
@@ -363,7 +363,6 @@
config/ns32k/tek6100.h
config/ns32k/tek6200.h
config/pa/elf.h
-config/pa/pa-gas.h
config/pa/pa-hiux.h
config/pa/pa-hpux.h
config/pa/pa-hpux10.h
@@ -405,7 +404,6 @@
config/rs6000/sysv4le.h
config/rs6000/vxppc.h
config/rs6000/xm-beos.h
-config/rs6000/xm-darwin.h
config/rtems.h
config/sh/elf.h
config/sh/rtems.h
next reply other threads:[~2001-05-23 0:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 0:16 Dennis Bjorklund [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 0:56 Dennis Bjorklund
2001-05-25 8:16 Zack Weinberg
2001-05-25 8:06 Zack Weinberg
2001-05-25 3:26 Joseph S. Myers
2001-05-25 3:06 Philipp Thomas
2001-05-25 2:56 Joseph S. Myers
2001-05-25 2:46 Philipp Thomas
2001-05-25 2:46 Philipp Thomas
2001-05-25 2:46 Philipp Thomas
2001-05-24 10:26 Zack Weinberg
2001-05-24 9:36 Joseph S. Myers
2001-05-24 9:26 Dennis Bjorklund
2001-05-24 9:16 Joseph S. Myers
2001-05-24 7:16 Dennis Bjorklund
2001-05-24 5:36 Joseph S. Myers
2001-05-24 4:36 Dennis Bjorklund
2001-05-24 1:36 Joseph S. Myers
2001-05-24 1:26 Zack Weinberg
2001-05-24 0:56 Joseph S. Myers
2001-05-24 0:46 Zack Weinberg
2001-05-23 10:36 Dennis Bjorklund
2001-05-23 0:56 Dennis Bjorklund
2001-05-23 0:26 Mark Mitchell
2001-05-22 23:06 Mark Mitchell
2001-05-22 22:56 Zack Weinberg
2001-05-22 22:36 Dennis Bjorklund
2001-05-22 12:56 Gabriel Dos Reis
2001-05-22 11:06 Zack Weinberg
2001-05-17 11:26 db
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=20010523071603.29099.qmail@sourceware.cygnus.com \
--to=db@zigo.dhs.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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).