From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Graf <tgraf@suug.ch>, ak@suse.de, netdev@oss.sgi.com
Subject: Re: [RFC] Extend netlink error codes
Date: Mon, 13 Sep 2004 08:26:13 +0200 [thread overview]
Message-ID: <20040913062613.GA12185@wotan.suse.de> (raw)
In-Reply-To: <20040912163744.52f95367.davem@davemloft.net>
On Sun, Sep 12, 2004 at 04:37:44PM -0700, David S. Miller wrote:
> On Sat, 11 Sep 2004 18:24:33 +0200
> Thomas Graf <tgraf@suug.ch> wrote:
>
> > > I don't think an very specific error like
> > > "CFQ subsystem parameter X is FOO, can be only upto BAR"
> > > can be nicely put into a global error file.
> >
> > True, I would really like to have such error messages.
>
> I'd love to have them too.
>
> But I know internationalization folks are going to
> scream, although it will obviously be better than
> no messages at all.
I actually don't think it will be a big issue for them.
They already translate messages by mapping text to other
text. The same thing could be done for kernel messages,
by just marking them in the kernel somehow that they
can be automatically extracted from the source and then
later mapping them to the translations in user space.
But I wouldn't do it until someone actually complains
about it.
-Andi
next prev parent reply other threads:[~2004-09-13 6:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 22:51 [RFC] Extend netlink error codes Thomas Graf
2004-09-10 23:07 ` David S. Miller
2004-09-11 1:38 ` jamal
2004-09-11 15:49 ` Thomas Graf
2004-09-11 15:58 ` Andi Kleen
2004-09-11 16:24 ` Thomas Graf
2004-09-11 16:50 ` Andi Kleen
2004-09-11 17:57 ` Thomas Graf
2004-09-11 18:48 ` Sam Leffler
2004-09-11 21:10 ` jamal
2004-09-13 20:36 ` Thomas Graf
2004-09-13 23:28 ` David S. Miller
2004-09-14 2:00 ` jamal
2004-09-12 23:37 ` David S. Miller
2004-09-13 6:26 ` Andi Kleen [this message]
2004-09-13 19:33 ` David S. Miller
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=20040913062613.GA12185@wotan.suse.de \
--to=ak@suse.de \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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 NNTP newsgroup(s).