From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.25-rc8
Date: Wed, 2 Apr 2008 07:50:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0804020748100.14670@woody.linux-foundation.org> (raw)
In-Reply-To: <18418.44094.156352.405647@cargo.ozlabs.ibm.com>
On Wed, 2 Apr 2008, Paul Mackerras wrote:
> Linus Torvalds writes:
>
> > I think the dirstat continues to be fairly informative, with arch/ and
> > drivers dominating as usual. And within arch, a fair amount of the line
> > noise are all those defconfigs. I wish we had some saner way of handling
> > that
>
> We (the arch maintainers) could try to do the bulk of the defconfig
> updates at about -rc2 or -rc3 time, if you'd prefer.
Well, that part isn't the one that I think is bothersome - I just wonder
if the whole "defconfig" mess is worth keeping with the kernel at _all_.
It also causes tons of noise whenever I happen to do something like "git
grep CONFIG_XYZZY" to see where some config variable is used etc.
So I was more wondering whether maybe there could be better ways of doing
that whole thing.
Linus
next prev parent reply other threads:[~2008-04-02 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:08 Linus Torvalds
2008-04-01 21:42 ` Paul Mackerras
2008-04-02 14:50 ` Linus Torvalds [this message]
2008-04-02 18:54 ` Adrian Bunk
2008-04-03 4:08 ` Paul Mackerras
2008-04-03 12:55 ` Josh Boyer
2008-04-03 18:18 ` Sam Ravnborg
2008-04-02 0:23 ` Stephen Rothwell
2008-04-02 3:03 ` Linus Torvalds
2008-04-02 3:09 ` Linus Torvalds
2008-04-02 18:57 ` Adrian Bunk
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=alpine.LFD.1.00.0804020748100.14670@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®