From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: stuff ready to be deleted?
Date: Mon, 28 May 2007 23:23:52 +0200 [thread overview]
Message-ID: <9a8748490705281423g6cccdc41n60dc48f25cff7598@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.99.0705281712190.10522@sigma.j-a-k-j.com>
On 28/05/07, John Anthony Kazos Jr. <jakj@j-a-k-j.com> 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 <jesper.juhl@gmail.com>
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
next prev parent reply other threads:[~2007-05-28 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 20:15 Robert P. J. Day
2007-05-28 20:24 ` Jesper Juhl
2007-05-28 21:14 ` John Anthony Kazos Jr.
2007-05-28 21:23 ` Jesper Juhl [this message]
2007-05-28 20:44 ` Oliver Pinter
2007-05-28 20:52 ` Robert P. J. Day
2007-05-28 23:49 ` Daniel Hazelton
2007-05-28 22:24 ` Bill Davidsen
2007-05-28 22:29 ` Jeff Garzik
2007-05-29 8:34 ` Alan Cox
2007-05-29 8:47 ` David Miller
2007-05-28 21:18 ` Jiri Slaby
2007-05-28 21:30 ` Jan Engelhardt
2007-05-28 22:25 ` Robert P. J. Day
2007-05-28 22:41 ` Robert P. J. Day
2007-05-29 6:09 ` Jan Engelhardt
2007-05-29 8:20 ` Robert P. J. Day
2007-05-29 8:46 ` David Miller
2007-05-29 7:56 ` Geert Uytterhoeven
2007-05-29 13:04 ` Finn Thain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a8748490705281423g6cccdc41n60dc48f25cff7598@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=jakj@j-a-k-j.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®