archive mirror
 help / color / mirror / Atom feed
From: Mariusz Mazur <>
To: lkml <>
Subject: [ANNOUNCE] linux-libc-headers
Date: Sat, 8 Jan 2005 16:13:27 +0100	[thread overview]
Message-ID: <> (raw)

Available at
- updated to 2.6.10
- switched to using svn and now ChangeLog is back :)
- some minor changes here and there (made some headers ansi C compatible)

Two weeks after 2.6.10, but you can blame Linus for releasing 2.6.10 just 
before Christmas.

Like I've said two months ago - my scripts for testing new versions now do 
separate asm-i386-ansi and asm-i386-noansi checks, so any ansi degradation in 
linux or asm-i386 (like the one from 2.6.9) won't go unnoticed.

One more thing - llh is now officially one year old (first commits are from 
December 2003). That's a long time for any hack to live. Especially a hack 
this big and one that even has a couple of vendor specific variants. A couple 
of discussions took place concerning this matter (in the last one Linus even 
said, that he'll be accepting patches) and still I see no movement. I'd 
really like to see glibc guys figuring out a way not to duplicate definitions 
and structures from linux and starting to submit patches. That'd be a really 
good (and much needed - glibc's and linux' headers conflict in lots of ugly 
ways) first step.

Happy New Year.

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:[~2005-01-08 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 15:13 Mariusz Mazur [this message]
2005-01-10 15:16 ` [ANNOUNCE] linux-libc-headers Randy.Dunlap
2005-01-12 10:49 ` Andrew Walrond
2005-01-12 11:11   ` Mariusz Mazur
2005-01-12 12:04     ` Andrew Walrond
2005-01-13  8:13     ` Andrew Walrond
2005-01-13  9:42       ` Mariusz Mazur
2005-01-13 11:00         ` Andrew Walrond
2005-01-13 11:46           ` Rahul Karnik
2005-01-13 11:51             ` Jakub Jelinek
2005-01-13 16:14               ` Rahul Karnik
2005-01-13 16:29               ` Mariusz Mazur
2005-01-13 12:18             ` Andrew Walrond

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).