LKML Archive on
help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Alan Cox <>
Cc: Martin Schwidefsky <>,
	Heiko Carstens <>,
	Andrew Morton <>,
	Greg Kroah-Hartman <>,,
Subject: Re: [GIT PULL/RESEND] kernel message catalog patches
Date: Mon, 27 Oct 2008 09:10:56 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 27 Oct 2008, Alan Cox wrote:
> > And as for the actual explanations: either they need to be totally outside 
> > the kernel (in a project of their own), or they'd need to be "kernel-doc" 
> > style things that are _in_ the source code. Not in Documentation/. Not 
> > separate from the printk() that they are associated with.
> You really don't want 32 languages in mixed left/right rendering with
> multiple fonts in your kernel source. At least not with most editing and
> viewing tools....

I do agree. Another issue is that quite often the actual line to be 
printed is likely fairly short, and often in an error path (so it's 
indented and in an inconvenient place), but the explanation - even for a 
_single_ language - may well be pretty involved and long.

Which is why I think for something like this, it really needs to be 
entirely outside. Because putting it inside the kernel simply isn't going 
to result in anything really useful. Either it can be close to the message 
and be updated reasonably (never mind that if we really do support 
multiple languages, that's not going to happen anyway, even if it's 
close), or it's going to be somewhere else and not be updated when changes 
happen - and then it migth as well be a separate project.

The 'separate project' is especially appropriate since any parsing won't 
be done by the kernel anyway, but by some ksyslog thing.


  reply	other threads:[~2008-10-27 16:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 14:50 [GIT PULL] " Martin Schwidefsky
2008-10-17  7:59 ` Martin Schwidefsky
2008-10-21  9:21   ` [GIT PULL/RESEND] " Heiko Carstens
2008-10-23 15:35     ` Linus Torvalds
2008-10-23 21:04       ` Heiko Carstens
2008-10-23 21:37         ` Linus Torvalds
2008-10-24 15:50           ` Heiko Carstens
2008-10-26 19:26           ` Martin Schwidefsky
2008-10-26 19:12             ` Linus Torvalds
2008-10-27 10:01               ` Martin Schwidefsky
2008-10-27 15:05                 ` Linus Torvalds
2008-10-27 15:52                   ` Martin Schwidefsky
2008-10-27 16:19                     ` Theodore Tso
2008-10-27 16:27                       ` Randy Dunlap
2008-10-28  8:25                         ` Martin Schwidefsky
2008-10-27 16:03                   ` Alan Cox
2008-10-27 16:10                     ` Linus Torvalds [this message]
2008-10-27 16:35                       ` Alan Cox
2008-10-27 19:36                       ` Theodore Tso

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [GIT PULL/RESEND] kernel message catalog patches' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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