From: Matthias Andree <matthias.andree@gmx.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Jeff Garzik <jeff@garzik.org>,
joe.korty@ccur.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.16
Date: Mon, 20 Mar 2006 23:52:32 +0100 [thread overview]
Message-ID: <20060320225232.GA30981@merlin.emma.line.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603201132070.3622@g5.osdl.org>
On Mon, 20 Mar 2006, Linus Torvalds wrote:
>
>
> On Mon, 20 Mar 2006, Jan Engelhardt wrote:
> > >
> > > strace should be using sanitized versions of the kernel headers, not directly
> > > including them verbatim...
> > >
> > Now, would not it be good for everyone if the in-kernel headers get
> > every bit of sanitation?
>
> Yes, we should strive for fairly sanitized headers. That said, Jeff is
> also right - people really generally shouldn't use the kernel headers
> directly.
It appears this message hasn't spread wide enough yet. When reporting an
inotify-related build failure, I heard back from the GNOMES I shouldn't
be using outdated glibc headers but kernel headers instead... apparently
there's more need for discussion.
(Not that I'd find gamin particularly sensible, since it's undocumented,
and attracted WAY too much attention because of its flaws like SIGSEGV
in applications, 100% CPU loops and other shortcomings not only in Linux
environments, but also on FreeBSD.)
--
Matthias Andree
next prev parent reply other threads:[~2006-03-20 22:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 6:23 Linus Torvalds
2006-03-20 12:02 ` 2.6.16.x will be a long-living kernel series Adrian Bunk
2006-03-20 12:05 ` Arjan van de Ven
2006-03-20 12:12 ` Adrian Bunk
2006-03-20 13:03 ` Arjan van de Ven
2006-03-24 0:22 ` Adrian Bunk
2006-03-20 19:22 ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04 ` Jeff Garzik
2006-03-20 19:25 ` Jan Engelhardt
2006-03-20 19:32 ` Joe Korty
2006-03-20 19:33 ` Linus Torvalds
2006-03-20 21:05 ` Andreas Schwab
2006-03-20 22:52 ` Matthias Andree [this message]
2006-03-22 5:22 ` Peter Williams
2006-03-22 6:31 ` Ashok Raj
2006-03-22 13:08 ` Ashok Raj
2006-03-22 13:25 ` Michal Piotrowski
2006-03-22 17:39 ` Rafael J. Wysocki
2006-03-22 17:54 ` Ashok Raj
2006-03-22 18:11 ` Rafael J. Wysocki
2006-03-22 18:27 ` Ashok Raj
2006-03-22 20:40 ` Rafael J. Wysocki
2006-03-22 21:00 ` Ashok Raj
2006-03-22 21:36 ` Rafael J. Wysocki
2006-03-22 22:27 ` Peter Williams
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09 ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01 9:18 ` netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error Adrian Bunk
[not found] <5Sm46-2a7-13@gated-at.bofh.it>
[not found] ` <5T455-7j-11@gated-at.bofh.it>
[not found] ` <5T5aR-1DN-23@gated-at.bofh.it>
[not found] ` <5Tbgl-2dp-43@gated-at.bofh.it>
2006-03-23 0:05 ` Linux v2.6.16 Bodo Eggert
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=20060320225232.GA30981@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=jeff@garzik.org \
--cc=jengelh@linux01.gwdg.de \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®