From: mru@kth.se (Måns Rullgård)
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.3.0
Date: Wed, 03 Mar 2004 13:49:31 +0100 [thread overview]
Message-ID: <yw1x8yiiksdg.fsf@kth.se> (raw)
In-Reply-To: <m37jy4cuaw.fsf@defiant.pm.waw.pl> (Krzysztof Halasa's message of "Mon, 01 Mar 2004 19:10:31 +0100")
Krzysztof Halasa <khc@pm.waw.pl> writes:
> The "non-problem" here is, IMHO, that the cleaning of kernel headers
> is quite trivial, and thus nobody is interested :-)
It usually is. I guess I'll start sending patches whenever I need to
change one to get something compiled. Usually it's so trivial that I
think I must have made a mistake somewhere else.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-03-03 12:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 18:42 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 [this message]
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
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=yw1x8yiiksdg.fsf@kth.se \
--to=mru@kth.se \
--cc=cfriesen@nortelnetworks.com \
--cc=khc@pm.waw.pl \
--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
all inboxes | Powered by JetHome®