mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Valdis.Kletnieks@vt.edu, Andre Tomt <andre@tomt.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: so ... what *are* candidates for removal?
Date: Wed, 2 May 2007 21:52:08 +1000	[thread overview]
Message-ID: <17976.31592.666183.353731@notabene.brown> (raw)
In-Reply-To: message from Robert P. J. Day on Wednesday May 2

On Wednesday May 2, rpjday@mindspring.com wrote:
> On Wed, 2 May 2007, John Anthony Kazos Jr. wrote:
> 
> argh.  the whole point of this discussion is to come to a *consensus*
> on what should be in that feature removal file.  there is no point in
> creating and submitting patches, either to update that file or remove
> kernel features, until enough people *agree*.
> 
> at the risk of being head-bangingly repetitive, that's what the wiki
> page is for:
> 
> http://fsdev.net/wiki/index.php?title=Stuff_to_be_removed
> 
> go.  read.  comment.  update.  add.  remove.  it's a wiki.  don't make
> me pull this car over and explain it.  :-)

Unfortunately, this community is not founded on the concept of
'wiki'.  It is founded on the concept of 'email'.  That is were most
discussions happen.

So if you want to start a discussion (and your topic certainly seems
relevant) I suspect you will get more participation if you keep it in
the mailing list.

So post a list of features that are apparently due for removal and ask
"can I actually get rid of these" (or whatever you want to ask).  and
then base on the response, do something else, maybe a revised list,
maybe a patch, maybe send it again in CAPITALS because nobody notice
when it was in lower-case :-)

Wiki's certainly have there place, but I don't think this is it.

NeilBrown

  reply	other threads:[~2007-05-02 11:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 15:01 Robert P. J. Day
2007-05-01 15:30 ` Andre Tomt
2007-05-01 16:37   ` Valdis.Kletnieks
2007-05-01 22:33     ` Stefan Richter
2007-05-02  8:28       ` Robert P. J. Day
2007-05-02  9:50         ` Stefan Richter
2007-05-02 10:14           ` John Anthony Kazos Jr.
2007-05-02 10:33             ` Stefan Richter
2007-05-02 10:58             ` Robert P. J. Day
2007-05-02 11:52               ` Neil Brown [this message]
2007-05-02 12:31                 ` Robert P. J. Day
2007-05-02 13:13                   ` Stefan Richter
2007-05-01 17:18 ` Jan Engelhardt

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=17976.31592.666183.353731@notabene.brown \
    --to=neilb@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=andre@tomt.net \
    --cc=jakj@j-a-k-j.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®