public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Mazur <mmazur@kernel.pl>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.7.0
Date: Thu, 24 Jun 2004 01:02:23 +0200	[thread overview]
Message-ID: <200406240102.23162.mmazur@kernel.pl> (raw)
In-Reply-To: <40DA0A42.3050205@nortelnetworks.com>

On czwartek, 24 czerwca 2004 00:54, Chris Friesen wrote:
> Not a high profile hacker, but you might try submitting a patch adding an
> include/user_abi directory (or whatever it should be called) and putting
> one of your files there, with patches to the original kernel header file to
> remove the userspace bits and include the new file.  That would maybe kick
> off some discussion.

I'm interested in guidelines, not discussion :)
Kernel guys had a couple of years since 2.4 for discussing this so something 
*must* have been agreed upon.


-- 
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 22:20 [ANNOUNCE] linux-libc-headers 2.6.7.0 Mariusz Mazur
2004-06-23 22:54 ` Chris Friesen
2004-06-23 23:02   ` Mariusz Mazur [this message]
2004-06-23 23:48     ` Chris Friesen
2004-06-24  5:58       ` Greg KH
2004-06-24  9:18         ` Jeff Garzik
2004-06-24 11:02           ` Mariusz Mazur
2004-06-24 13:53         ` Andries Brouwer
2004-06-24 19:29           ` Sam Ravnborg
2004-06-23 23:17 ` Jeff Garzik
2004-06-23 23:30   ` Mariusz Mazur
2004-06-24 16:43   ` Krzysztof Halasa
2004-06-25  9:25     ` Martin Waitz
2004-06-25 10:02       ` Andries Brouwer
2004-06-25 11:33 ` Rob Landley

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=200406240102.23162.mmazur@kernel.pl \
    --to=mmazur@kernel.pl \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.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