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.7.0
Date: Wed, 23 Jun 2004 18:54:58 -0400	[thread overview]
Message-ID: <40DA0A42.3050205@nortelnetworks.com> (raw)
In-Reply-To: <200406240020.39735.mmazur@kernel.pl>

Mariusz Mazur wrote:

> Llh is all good and nice, cause it works (most of the times anyway), but 
> with
> every new release the possibility of desync from kernel increases - 
> downfalls
> of maintaining it as a separate package. Could anybody point me to some
> conclusions about how the thing should be done The Right Way (preferably 
> with
> some input from high profile kernel hackers, so I can have some assurance
> that once something gets done it will get merged)?

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.

Chris

  reply	other threads:[~2004-06-23 22:55 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 [this message]
2004-06-23 23:02   ` Mariusz Mazur
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=40DA0A42.3050205@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