From: David Woodhouse <dwmw2@infradead.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: torvalds@osdl.org, akpm@osdl.org, sam@ravnborg.org,
arnd@arndb.de, jbailey@ubuntu.com,
Tim Yamin <plasmaroo@gentoo.org>,
Bernhard Rosenkraenzer <bero@arklinux.org>,
alan@lxorguk.ukuu.org.uk, Thorsten Kukuk <kukuk@suse.de>,
Clint Adams <schizo@debian.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT *] make headers_install
Date: Thu, 29 Jun 2006 01:22:01 +0100 [thread overview]
Message-ID: <1151540522.18930.16.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20060628234450.GB5074@linux-mips.org>
On Thu, 2006-06-29 at 00:44 +0100, Ralf Baechle wrote:
> Thanks for the time you've been pouring into this. Copying kernel
> header into applications clearly didn't work too well, especially for
> arch stuff (two dozen and counting ...) it was a pain and each
> distribution had different sets of hacked kernel headers.
The technical part wasn't very time-consuming at all. Arnd provided the
basic implementation, and I just tweaked it a little to use unifdef and
be a bit more selective about what we export. It's probably taken less
time than it would have done to get Fedora's 'glibc-kernheaders' package
into shape manually the way it always used to be done -- and it'll
_certainly_ be a Godsend for future updates.
The time-consuming part was chasing up those who look after similar
packages in other distributions and making sure they were happy enough
with the principle too -- tracking them down on IRC when they ignored my
emails.
The current hurdle seems to be getting Linus to take it or at least
comment, now that everyone _else_ seems to be fairly much in agreement.
I'm hoping we don't have to let it drag on till the Kernel Summit.
--
dwmw2
next prev parent reply other threads:[~2006-06-29 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 22:12 David Woodhouse
2006-06-28 23:44 ` Ralf Baechle
2006-06-29 0:22 ` David Woodhouse [this message]
2006-07-02 9:57 David Woodhouse
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=1151540522.18930.16.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=bero@arklinux.org \
--cc=jbailey@ubuntu.com \
--cc=kukuk@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=plasmaroo@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=sam@ravnborg.org \
--cc=schizo@debian.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®