First things first, I would like to know what prompted the change from 2.4 to 2.6 kernels. I know that the change had to do with the development version, the 2.5 tree and the massive amounts of patches distros had to carry. Aside from this i think it was also the scheduler changes that prompted the 2.6 version, but I don't know all that much about it and any other comments about the change would be great. Second I wanted to talk about the linux 2.7.x kernel, whats in the making or maybe even not started, that could prompt a change to a 2.7 version kernel, i know that a lot of good changes are going into the kernel as part of the rcX kernels in the 2.6 version. Would we continue to see 2.6 kernels until some big problem shows its head and we all go "oh sh**" and then change something so massive that it prompts the change or are we going to continue with the 2.6 tree. I just want to get some information and peoples opinions on this, just to see where things are headed. -Stoyan G --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Joe Perches | [PATCH 011/148] include/asm-x86/bug.h: checkpatch cleanups - formatting only |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Tony Lindgren | [PATCH 29/90] ARM: OMAP: Palm Tungsten|T support |
git: | |
| Jakub Narebski | Re: VCS comparison table |
| Linus Torvalds | Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins |
| Jon Smirl | ! [rejected] master -> master (non-fast forward) |
| Scott Chacon | Re: git-scm.com |
| Richard Stallman | Real men don't attack straw men |
| Christophe Rioux | OpenBSD as host for VMWare Server |
| Eduardo Meyer | OpenBGP "state change OpenSent -> Active, reason: Connection closed" trouble |
| Jerome Santos | sshd.config and AllowUsers |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jiri Olsa | [PATCH] net: fix race in the receive/select |
| Wang Chen | [PATCH]&[Question] netdevice: Use netdev_priv() |
| Willy Tarreau | Re: [PATCH] tcp: splice as many packets as possible at once |
