Oliver Neukum <oliver@neukum.org> writes:I was thinking about a mailing list / database service instead: - source file/directory-based (e.g. someone could maintain whole drivers/, someone else drivers/char and others drivers/char/asdfg.[ch]) - people would be able to add themselves as "observers" using mail and/or HTML interface - sending a patch would automatically trigger Cc: to all people registered as maintainers (or "observers") for the files modified - full recipient list would be present in mail sent by the service, so the following discussion wouldn't need it anymore. It would be used only for posting patches. - as such, I don't expect a need for spam filtering - messages containing no patch would be rejected in the SMTP session. Pro: no more missing Cc:, no more manual lookups and guessing, you just Cc: the service, possibility for "observers". Con: another thing to create and maintain, you don't immediately know who exactly has been sent a copy. I think I could create a test service but after the test phase it should probably go to some machine more reliable/able than mine. Comments? -- Krzysztof Halasa --
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Stoyan Gaydarov | From 2.4 to 2.6 to 2.7? |
| Andi Kleen | [PATCH] [4/50] x86: add cpu codenames for Kconfig.cpu |
| Greg Kroah-Hartman | [PATCH 013/196] Documentation: Replace obsolete "driverfs" with "sysfs". |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: HTB accuracy for high speed |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
