From: Sam Ravnborg <sam@ravnborg.org>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kbuild update
Date: Fri, 4 Jan 2008 15:39:53 +0100 [thread overview]
Message-ID: <20080104143953.GA30536@uranus.ravnborg.org> (raw)
In-Reply-To: <20080104132316.GA2485@hacking>
On Fri, Jan 04, 2008 at 09:23:16PM +0800, WANG Cong wrote:
>
> {snip}
>
> >TODO items (from my mailbox - I have plenty more)
> >=================================================
> >- asm-offset useable from modules (Oleg had a half backed solution)
> >- modpost should use err(), warn() etc (suggestyed by Rusty)
> >- less kernel hardcoding in kconfig (Rob Landley)
> >- emit dependencies from "depends" (Bernhard Fischer)
> >- fix select (whatever that means)
> >- allow kconfig to accept overrides (Jan Engelhart)
> > maybe there is a patch, needs followup
> >- document kernel build better (Andreas Hermann)
> > just a start, more is needed
> >- save ARCH and CROSSCOMPILE
> > requires major surgery to do correct - we use CC too early
> >- i18n patch for mconf and friends (from Kernel Translator project)
> > is old but several bits of it needs to be applied to better support i18n
>
> Hmm, I glanced at that project. It's old and seems freezed now.
> I don't know if people still have interests in the i18n of kconfig.
> If so, I think I can help with the Chinese part. ;)
>From the off-list communication I have had there is indeed an interest.
It sort of stopped at one point due to missing integration in mainline.
What I refer to is mostly the mconf.c bits, but I would also like to
see what lkml says to a sample of .po files included in the kernel
for a number of languages.
One criteria to get a .po file integrated could be at least 10% of the
strings translated or similar.
Sam
next prev parent reply other threads:[~2008-01-04 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 21:32 Kbuild update Sam Ravnborg
2008-01-03 21:46 ` Josh Boyer
2008-01-03 22:33 ` Jan Engelhardt
2008-01-04 19:43 ` Sam Ravnborg
2008-01-04 20:09 ` Jan Engelhardt
2008-01-04 13:23 ` WANG Cong
2008-01-04 14:39 ` Sam Ravnborg [this message]
2008-01-05 5:48 ` Adrian Bunk
2008-01-06 14:26 ` WANG Cong
2008-01-06 15:07 ` Adrian Bunk
2008-01-06 15:45 ` Sam Ravnborg
2008-01-09 2:32 ` WANG Cong
2008-01-09 5:18 ` Sam Ravnborg
2008-01-09 2:28 ` WANG Cong
2008-01-06 21:41 ` translations (Re: Kbuild update) Oleg Verych
2008-01-06 22:03 ` Sam Ravnborg
2008-01-09 2:22 ` WANG Cong
2008-01-09 13:50 ` Oleg Verych
2008-01-15 1:33 ` WANG Cong
-- strict thread matches above, loose matches on Subject: below --
2007-09-16 9:47 kbuild update Sam Ravnborg
2007-09-16 12:58 ` Robert P. J. Day
2007-09-16 15:13 ` Sam Ravnborg
2007-09-16 15:21 ` Robert P. J. Day
2007-09-16 19:23 ` Andrew Morton
2007-09-16 20:38 ` Sam Ravnborg
2007-06-03 20:36 Sam Ravnborg
2007-06-03 20:51 ` Sam Ravnborg
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=20080104143953.GA30536@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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).