netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Andi Kleen <ak@suse.de>
Cc: tgraf@suug.ch, ak@suse.de, netdev@oss.sgi.com
Subject: Re: [RFC] Extend netlink error codes
Date: Mon, 13 Sep 2004 12:33:08 -0700	[thread overview]
Message-ID: <20040913123308.00686fb2.davem@davemloft.net> (raw)
In-Reply-To: <20040913062613.GA12185@wotan.suse.de>

On Mon, 13 Sep 2004 08:26:13 +0200
Andi Kleen <ak@suse.de> wrote:

> 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. 

I understand, but I'm specifically talking about this
"synchronization" issue.

Anyways, I think strings are fine.

      reply	other threads:[~2004-09-13 19:33 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
2004-09-13 19:33         ` David S. Miller [this message]

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=20040913123308.00686fb2.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ak@suse.de \
    --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).