On 28/05/07, John Anthony Kazos Jr. <[EMAIL PROTECTED]> wrote:
> > i'm trying to keep track of kernel janitor projects that involve
> > removing dead content from the tree:
> >
> > http://fsdev.net/wiki/index.php?title=Kernel_Janitor%27s_Todo_List
> >
> > currently, the list contains the items:
> >
> > * 1 Legacy power management
> > * 2 PCMCIA IOCTL support
> > * 3 Traffic shaper
> > * 4 Traffic policing
> > * 5 Userspace queueing via NETLINK
> > * 6 ebt: ulog support
> > * 7 MOXA SmartIO support
> > * 8 Old I2O ioctls
> > * 9 Stallion drivers
> > * 10 SDL RISCom/8 support
> > * 11 Macintosh M68K support
> > * 12 Commodore A2232 serial support
> > * 13 CONFIG_FORCED_INLINING
> > * 14 kernel_thread()
> >
> > which of the above are legitimate candidates for removal? which are
> > already underway in someone's local tree? anything else that can
> > be added? etc, etc.
> >
>
> Take a look at Documentation/feature-removal-schedule.txt
> Some of that stuff is already listed there along with who is in charge
> of removing it and when.
Let's not get in that catfight again. That file has been demonstrated to
be half too premature and half completely obsolete. He's asking for which
things should he start generating and sending patches and expect them to
not be ignored or angrily shot down. feature-removal-schedule.txt does not
provide this information, again as has been demonstrated.
Of course, it would be great if it were accurate and -did- provide that
information.
Well, at least that file does give him a clue as to who to talk to
about removal of some of the items on the list. It may not be as
up-to-date as it ought to be, but it's still a source of
information/contact info.
--
Jesper Juhl <[EMAIL PROTECTED]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
