public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.3.0
Date: Thu, 04 Mar 2004 18:32:00 -0500	[thread overview]
Message-ID: <4047BC70.5050109@nortelnetworks.com> (raw)
In-Reply-To: 200403042352.28592.mmazur@kernel.pl

Mariusz Mazur wrote:
> On Thursday 04 of March 2004 22:27, Chris Friesen wrote:
> 
>>And how do you propose to handle a kernel developer that wants to add a
>>new feature (a scheduling class, for instance) and make it available to
>>userspace apps?
>>
> 
> Dunno. That's something one should ask the glibc people.

That's exactly my point.  I don't *want* to have to ask the glibc people.

I want to have the kernel ABI headers ship with the kernel, and only 
with the kernel.

I want to be able to change one header file, recompile my kernel, 
recompile my app, reboot, and pick up the change.  glibc should not even 
be a factor.

Chris




-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2004-03-04 23:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 18:42 [ANNOUNCE] linux-libc-headers 2.6.3.0 Mariusz Mazur
2004-02-29 20:19 ` H. Peter Anvin
2004-02-29 20:30   ` Mariusz Mazur
2004-02-29 21:03     ` H. Peter Anvin
2004-02-29 21:21       ` Mariusz Mazur
2004-02-29 21:33         ` Måns Rullgård
2004-03-01 14:42           ` Chris Friesen
2004-03-01 18:10             ` Krzysztof Halasa
2004-03-03 12:49               ` Måns Rullgård
2004-03-03 15:22               ` Sam Ravnborg
2004-03-03 16:49                 ` Krzysztof Halasa
2004-03-04 16:50                   ` Jeff Garzik
2004-03-04 18:49                     ` [Linuxabi] " H. Peter Anvin
2004-03-04  4:43                 ` [Linuxabi] " H. Peter Anvin
2004-03-03 18:08               ` [ANNOUNCE] " Mariusz Mazur
2004-03-03 19:20                 ` Grzegorz Kulewski
2004-03-04 14:13                 ` Krzysztof Halasa
2004-03-04 20:49                   ` Mariusz Mazur
2004-03-04 21:27                     ` Chris Friesen
2004-03-04 22:52                       ` Mariusz Mazur
2004-03-04 23:32                         ` Chris Friesen [this message]
2004-03-05 17:02                     ` Krzysztof Halasa
2004-03-05 23:44                       ` Grzegorz Kulewski
2004-03-06 22:30                         ` Krzysztof Halasa
2004-03-07  1:15                           ` Paul Jackson
2004-03-07 19:00                             ` Krzysztof Halasa
2004-03-08  1:28                               ` Paul Jackson
2004-03-08 15:03                                 ` Krzysztof Halasa
2004-03-08 15:37                                   ` Chris Friesen
2004-03-08 20:27                                     ` Krzysztof Halasa
2004-02-29 21:25     ` Benjamin Herrenschmidt

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=4047BC70.5050109@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmazur@kernel.pl \
    /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