From: Christoph Hellwig <hch@infradead.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
davidm@hpl.hp.com, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: make AT_SYSINFO platform-independent
Date: Sat, 11 Jan 2003 19:13:47 +0000 [thread overview]
Message-ID: <20030111191347.A5413@infradead.org> (raw)
In-Reply-To: <3E206B41.2090203@redhat.com>; from drepper@redhat.com on Sat, Jan 11, 2003 at 11:06:41AM -0800
On Sat, Jan 11, 2003 at 11:06:41AM -0800, Ulrich Drepper wrote:
> > glibc release yet and no stable kernel release yet with that number.
>
> Of course there is. You better don't talk about thinks you don't know.
The latest glibc release, 2.3.1 does not contain AT_SYSINFO support.
I might be not as briliant as you but I'm certainly not stupid.
> > Interfaces change during 2.5 (see the sys_security and largepage syscall
> > removal) and that's okay. There was no nastiness involved in my
> > suggestion.
>
> You don't get it. I would never have distributed binaries with the
> current code if it wouldn't have been requested along with the guarantee
> that the current interface is stable and final.
Sorry, but having not yet fixed interfaces is the whole point of
development kernels. If vendors can't resist using the latest and gratest
features they get screwed. RH seems to have the manpower to maintain their
mistakes for a long enough time, so what's the issue?
next prev parent reply other threads:[~2003-01-11 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 6:45 make AT_SYSINFO platform-independent David Mosberger
2003-01-11 11:07 ` Christoph Hellwig
2003-01-11 18:43 ` Linus Torvalds
2003-01-11 18:52 ` Ulrich Drepper
2003-01-11 18:57 ` Christoph Hellwig
2003-01-11 19:06 ` Ulrich Drepper
2003-01-11 19:13 ` Christoph Hellwig [this message]
2003-01-11 19:24 ` Ulrich Drepper
2003-01-11 19:30 ` Christoph Hellwig
2003-01-11 19:29 ` Linus Torvalds
2003-01-11 19:36 ` Christoph Hellwig
2003-01-11 19:36 ` David Mosberger
2003-01-12 0:21 ` Alan Cox
2003-01-11 23:47 ` Jeff Garzik
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=20030111191347.A5413@infradead.org \
--to=hch@infradead.org \
--cc=davidm@hpl.hp.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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