[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200808141153.03269.rusty@rustcorp.com.au>
Date: Thu, 14 Aug 2008 11:53:01 +1000
From: Rusty Russell <rusty@...tcorp.com.au>
To: "Tim Hockin" <thockin@...kin.org>
Cc: "Martin Schwidefsky" <schwidefsky@...ibm.com>,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
lf_kernel_messages@...ts.linux-foundation.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Michael Holzheu" <holzheu@...ibm.com>,
"Gerrit Huizenga" <gh@...ibm.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
"Jan Kara" <jack@...e.cz>, "Pavel Machek" <pavel@....cz>,
"Sam Ravnborg" <sam@...nborg.org>, "Joe Perches" <joe@...ches.com>,
"Jochen Voß" <jochen.voss@...glemail.com>,
"Kunai Takashi" <kunai@...ux-foundation.jp>,
"Tim Bird" <tim.bird@...sony.com>
Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros.
On Wednesday 13 August 2008 17:04:11 Tim Hockin wrote:
> But there are a number of places that have different strings for the
> same meaning: "Can't" vs "can't" vs "can not" vs "failed to", etc.
>
> This is a big part of what hurts us - you end up with lots of loose
> regexes when parsing logs.
Well, if they're to be the same messages under the manual-numbering scheme,
someone has to verify that they are really the same anyway. Not much more
work to simply fix them in that case, is it?
If it improves normal kernel messages, then everyone wins.
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists