* Stephen Rothwell <sfr@canb.auug.org.au> wrote:hm, i do searches on lkml before posting patches but i cannot do searches on _every_ mailing list where patches might show up. There's just 30 hours in a day ;-) perhaps linux-next should propagate all add-on fix patches it is carrying against subsystem trees if they are still relevant to -git, once the subsystem tree goes to -git, and re-post them to lkml in that case, to avoid duplicative work? Once it's on lkml i think most subsystem maintainers will find any missing patches. yeah. Ingo --
| Alexandre Oliva | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Eric W. Biederman | Re: [net-2.6.24][patch 2/2] Dynamically allocate the loopback device |
| Ingo Molnar | Re: containers (was Re: -mm merge plans for 2.6.23) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Michael Riepe | Re: 2.6.27.19 + 28.7: network timeouts for r8169 and 8139too |
