From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: kettenis@gnu.org, gdb@sources.redhat.com
Subject: Re: Trimming the CVS "gdb" module
Date: Wed, 20 Oct 2004 15:11:00 -0000 [thread overview]
Message-ID: <01c4b660$Blat.v2.2.2$193a8e00@zahav.net.il> (raw)
In-Reply-To: <41759B30.3070907@gnu.org> (message from Andrew Cagney on Tue, 19 Oct 2004 18:54:40 -0400)
> Date: Tue, 19 Oct 2004 18:54:40 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: kettenis@gnu.org, gdb@sources.redhat.com
>
> Are there any current GNU systems that have this problem?
I don't know. I was talking about non-GNU systems, since you said
that GNU systems always come with gettext.
> Are there any current non-GNU systems have this problem?
Any non-GNU system where there's no gettext installed would be
affected. All the Unix and Windows boxes I'm working on are like
that.
> PS: Up to and including 6.2, GDB didn't even need intl/ yet it was
> bundling it. It was an artifact inherited from the Cygnus tree.
Like I said, I'm not opposed to what you did if we intend to add it
back at some future date, when GDB will support gettext and message
catalogs. What worries me is that it sounds like we intend to remove
the i18n stuff for good.
next prev parent reply other threads:[~2004-10-20 4:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:45 Andrew Cagney
2004-10-08 10:10 ` Eli Zaretskii
2004-10-13 4:52 ` Andrew Cagney
2004-10-13 13:45 ` Eli Zaretskii
2004-10-14 4:48 ` Mark Kettenis
2004-10-14 4:53 ` Eli Zaretskii
2004-10-19 19:55 ` Andrew Cagney
2004-10-19 20:34 ` Eli Zaretskii
2004-10-19 22:55 ` Mark Kettenis
2004-10-20 2:29 ` Eli Zaretskii
2004-10-20 4:52 ` Andrew Cagney
2004-10-20 15:11 ` Eli Zaretskii [this message]
2004-10-20 18:29 ` Andrew Cagney
2004-10-20 22:21 ` Eli Zaretskii
2004-10-20 23:25 ` Daniel Jacobowitz
2004-10-21 14:51 ` Eli Zaretskii
2004-10-22 10:09 ` Daniel Jacobowitz
2004-10-19 18:28 ` Andrew Cagney
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='01c4b660$Blat.v2.2.2$193a8e00@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@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