[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3ece790808130750x37e44e48u125a95780ff32d8a@mail.gmail.com>
Date: Wed, 13 Aug 2008 07:50:14 -0700
From: "Tim Hockin" <thockin@...kin.org>
To: "Pavel Machek" <pavel@...e.cz>
Cc: "Rusty Russell" <rusty@...tcorp.com.au>,
"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>, "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 Wed, Aug 13, 2008 at 12:13 AM, Pavel Machek <pavel@...e.cz> wrote:
> Hi!
>
>> 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.
>
> Do you have examples?
>
> That wastes space in bzImage (and hints of duplicated code), so we may
> want to fix it anyway.
I can look for the specific examples. I just saw the regexes we use
this week and was taken aback at how they have been loosened for these
sorts of cases.
--
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