All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	James Simmons <jsimmons@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Why moving driver includes ?
Date: Wed, 2 Apr 2003 20:40:26 -0500	[thread overview]
Message-ID: <20030402204026.A15082@devserv.devel.redhat.com> (raw)
In-Reply-To: <3E8B8F31.5030407@redhat.com>; from drepper@redhat.com on Wed, Apr 02, 2003 at 05:32:33PM -0800

> Date: Wed, 02 Apr 2003 17:32:33 -0800
> From: Ulrich Drepper <drepper@redhat.com>

> > Yeah, but what does it have to do with kernel? You should have
> > gotten Uli to add them to glibc.
> 
> Headers like have no place in glibc either.  There should be one or more
> separate packages which distribute kernel headers.

I can see your point, but imagine how many packages this is
going to create. Shall we plead with Arjan to maintain
glibc-kernelheaders as a community package, to be a clearinghouse
for these things?

-- Pete

  reply	other threads:[~2003-04-03  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1049324411.25620.linux-kernel2news@redhat.com>
2003-04-03  0:45 ` Why moving driver includes ? Pete Zaitcev
2003-04-03  1:32   ` Ulrich Drepper
2003-04-03  1:40     ` Pete Zaitcev [this message]
2003-04-04 13:30       ` Christoph Hellwig
2003-03-28  4:48 Framebuffer fixes James Simmons
2003-03-28 13:18 ` Why moving driver includes ? Benjamin Herrenschmidt
2003-03-28 13:18   ` Benjamin Herrenschmidt
2003-04-02 22:56   ` James Simmons

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=20030402204026.A15082@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=drepper@redhat.com \
    --cc=jsimmons@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.