From: Dave Jones <davej@codemonkey.org.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix undeclared NULL in timer.h
Date: Mon, 4 Nov 2002 14:27:03 +0000 [thread overview]
Message-ID: <20021104142703.GA20234@suse.de> (raw)
In-Reply-To: <200211041139.gA4Bdjp32237@Port.imtp.ilyichevsk.odessa.ua>
On Mon, Nov 04, 2002 at 02:31:39PM -0200, Denis Vlasenko wrote:
> The whole problem of #include forest going out of control
> needs some clever solution or we will eternally chase missing
> .h files
Doing an untangle at this point is pretty much a waste of effort.
As we get closer to stabilising, we can regenerate the dependancy
graphs and see what looks out of place again.
Adding lots of #include's isn't an issue as long as those includes
aren't sucking in 200 others.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
prev parent reply other threads:[~2002-11-04 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 7:32 [PATCH] Fix undeclared NULL in timer.h Rusty Russell
2002-11-04 16:31 ` Denis Vlasenko
2002-11-04 14:27 ` Dave Jones [this message]
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=20021104142703.GA20234@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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