From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: What's in kbuild.git for 2.6.19
Date: Sun, 13 Aug 2006 13:57:54 -0700 [thread overview]
Message-ID: <20060813135754.3c4a83a6.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060813135426.8211204c.rdunlap@xenotime.net>
On Sun, 13 Aug 2006 13:54:26 -0700 Randy.Dunlap wrote:
> On Sun, 13 Aug 2006 21:45:03 +0200 Sam Ravnborg wrote:
>
> > Just a quick intro to what is pending in kbuild.git/lxdialog.git
> > for 2.6.19. And a short status too.
> >
> > o try the new "make V=2" thing. It tells why a target got
> > rebuild. It is good to catch those "why the heck did
> > kbuild rebuild that much after changing just a tine CONFIG_
> > option".
>
> Thanks, will use it.
>
> > Jan Engelhardt:
> > kconfig: linguistic fixes for
> > Documentation/kbuild/kconfig-language.txt kbuild: linguistic fixes
> > for Documentation/kbuild/modules.txt kbuild: linguistic fixes for
> > Documentation/kbuild/makefiles.txt
>
> Were any of these used?
> http://marc.theaimsgroup.com/?l=linux-kernel&m=115410865910922&w=2
and even that has a few typos :(
---
~Randy
next prev parent reply other threads:[~2006-08-13 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 19:45 What's in kbuild.git for 2.6.19 Sam Ravnborg
2006-08-13 20:54 ` Randy.Dunlap
2006-08-13 20:57 ` Randy.Dunlap [this message]
2006-08-13 21:09 ` Sam Ravnborg
2006-08-13 22:00 ` Randy.Dunlap
2006-08-14 3:38 ` [PATCH] kbuild: more doc. cleanups Randy.Dunlap
2006-08-14 7:02 ` What's in kbuild.git for 2.6.19 Keith Owens
2006-08-14 19:02 ` Siddha, Suresh B
2006-08-15 3:53 ` Keith Owens
2006-08-15 6:25 ` Keith Owens
2006-08-15 15:16 ` Sam Ravnborg
2006-08-18 8:26 ` Greg Schafer
2006-08-18 17:13 ` Sam Ravnborg
2006-08-18 22:12 ` Greg Schafer
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=20060813135754.3c4a83a6.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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