From: Matthew Wilcox <matthew@wil.cx>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Adrian Bunk <bunk@kernel.org>,
linux-kbuild@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: "Anyone who likes complexity and fuzzy logic" (Re: [PATCH] headerdep:...)
Date: Wed, 30 Apr 2008 11:38:37 -0600 [thread overview]
Message-ID: <20080430173837.GP14976@parisc-linux.org> (raw)
In-Reply-To: <E1JrGYO-0000Li-K6@flower>
On Wed, Apr 30, 2008 at 07:57:16PM +0200, Oleg Verych wrote:
> Why? Why GNU C compiler developers didn't do such (obviously useful)
> tool? C compiler (some part of it) *is* responsible for parsing,
> tokenizing, etc. Why there is development of never-ending buggy
> optimizations only[0]?
Shut up.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-04-30 17:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 13:45 [PATCH] headerdep: a tool for detecting inclusion cycles in header file Vegard Nossum
2008-04-26 13:59 ` Pekka Enberg
2008-04-26 14:17 ` Vegard Nossum
2008-04-26 14:22 ` Nick Andrew
2008-04-26 18:03 ` Jan Engelhardt
2008-04-26 15:00 ` Adrian Bunk
2008-04-26 15:21 ` Julia Lawall
2008-04-26 15:30 ` Vegard Nossum
2008-04-26 15:25 ` Vegard Nossum
2008-04-26 16:17 ` Matthew Wilcox
2008-04-26 16:38 ` Adrian Bunk
2008-04-30 17:57 ` "Anyone who likes complexity and fuzzy logic" (Re: [PATCH] headerdep:...) Oleg Verych
2008-04-30 17:38 ` Matthew Wilcox [this message]
2008-04-26 16:44 ` [PATCH] headerdep: a tool for detecting inclusion cycles in header file Adrian Bunk
2008-04-26 16:57 ` Vegard Nossum
2008-04-26 17:23 ` Adrian Bunk
2008-04-26 17:55 ` Vegard Nossum
2008-04-26 18:11 ` Jan Engelhardt
2008-04-26 18:26 ` 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=20080430173837.GP14976@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bunk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=penberg@cs.helsinki.fi \
--cc=sam@ravnborg.org \
--cc=vegard.nossum@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