Hi Adrian.The patches you submit touches all parts of the kernel tree. And you do a good job in finding the relevant receivers. To me you are partly in the saem situation as Andrew in that you handle a great deal of patches touching a lot of different subsystems. We all know that the patch acceptance ratio differ a lot between the different maintainers and the way Andrew deals with this seems quite effective. After enough tries Andrew just submit the pacthes himself direct to Linus. But almost never without trying to get the relevant Maintainer to take it first. So in your position I would keep all patches in a place so they can be sucked into -next and regular spam the relevant amintainers with their patches. When the merge window opens then submit the rest to Linus with a noe that they have been sent to Maintainers without any feedback previously. This is not far away from what you do now and should not create that big frustrations (I hope). Sam --
| David Miller | [GIT]: Networking |
| Andi Kleen | Please pull ACPI updates |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Fred . | Please add ZFS support (from GPL sources) |
git: | |
| Theodore Ts'o | Any objectsions to enhancing git-log to show tags/branch heads? |
| Alex R.M. Turner | Re: Problem with a push |
| Sebastian Schuberth | git on Cygwin: Not a valid object name HEAD |
| Dan Farina | backup or mirror a repository |
| Theo de Raadt | That whole "Linux stealing our code" thing |
| Jeff Ross | U320 Drive on U160 controller? |
| Richard Stallman | Real men don't attack straw men |
| Bertram Scharpf | First install: Grub doesn't find partitions |
| Jim Winstead Jr. | Re: Root Disk/Book Disk Compatibility |
| Desmond A. Kirkpatrick | ATI GUP bug with Linux 'tickler' |
| erc | HARDWARE COMPATIBILITY LIST |
| L.G. Ted Stern | Psfrag.sty in TeX, ext2fs |
