From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Dave Jones <davej@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.5.2.7: io.h cleanup and userspace nudge
Date: Fri, 04 Jan 2002 13:35:06 -0500 [thread overview]
Message-ID: <3C35F5DA.61A57A3E@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201041916490.20620-100000@Appserv.suse.de> <3C35F290.140BB2C7@mandrakesoft.com> <200201041831.g04IVAD23320@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
> Please test this change on a libc5 system before unleashing a
> potential horror. All the world *is not* glibc!
(1) This is a devel series, the time for such changes, and (2) and it's
easy enough for libc5 systems to include their own sanitized copy of
kernel headers just like MDK, RHAT, and others are doing now for glibc.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2002-01-04 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 17:47 PATCH 2.5.2.7: io.h cleanup and userspace nudge Jeff Garzik
2002-01-04 18:00 ` Dave Jones
2002-01-04 18:12 ` Jeff Garzik
2002-01-04 18:18 ` Dave Jones
2002-01-04 18:20 ` David Woodhouse
2002-01-04 18:39 ` Alan Cox
2002-01-04 18:46 ` including kernel headers (was Re: PATCH 2.5.2.7: io.h cleanup and userspace nudge) Jeff Garzik
2002-01-04 18:21 ` PATCH 2.5.2.7: io.h cleanup and userspace nudge Jeff Garzik
2002-01-04 18:24 ` Dave Jones
2002-01-04 18:31 ` Richard Gooch
2002-01-04 18:35 ` Jeff Garzik [this message]
2002-01-04 18:40 ` Dave Jones
2002-01-04 18:41 ` Richard Gooch
2002-01-04 19:16 ` Mike Castle
2002-01-04 23:28 ` Reid Hekman
2002-01-04 18:19 ` Oliver Xymoron
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=3C35F5DA.61A57A3E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=torvalds@transmeta.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