linux-libc-headers-2.6.12.0
Version increment (2.6.9.0)
Change History
(15)
Summary: |
linux-libc-headers-2.6.9.0 → linux-libc-headers-2.6.9.1
|
Resolution: |
→ fixed
|
Status: |
new → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Summary: |
linux-libc-headers-2.6.9.1 → linux-libc-headers-2.6.10.0
|
Status: |
reopened → assigned
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Summary: |
linux-libc-headers-2.6.10.0 → linux-libc-headers-2.6.11.0
|
Status: |
reopened → assigned
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Summary: |
linux-libc-headers-2.6.11.0 → linux-libc-headers-2.6.11.1
|
Status: |
reopened → assigned
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Summary: |
linux-libc-headers-2.6.11.1 → linux-libc-headers-2.6.11.2
|
Resolution: |
→ fixed
|
Status: |
reopened → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Summary: |
linux-libc-headers-2.6.11.2 → linux-libc-headers-2.6.12.0
|
Resolution: |
→ fixed
|
Status: |
reopened → closed
|
Version increment 2.6.9.1 as mentioned at http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/0501.html. Of particular note:
"And my scripts that automatically check new releases for broken headers will use -ansi flag from now on, so these types of bugs should not happen anymore."