From: Ken Brownfield <ken@irridia.com>
To: Luigi Genoni <kernel@Expansa.sns.it>
Cc: Christoph Hellwig <hch@infradead.org>,
"David S. Miller" <davem@redhat.com>,
dank@kegel.com, arjanv@redhat.com, marcelo@conectiva.com.br,
khttpd-users@alt.org, linux-kernel@vger.kernel.org
Subject: Re: khttpd rotten?
Date: Fri, 10 May 2002 19:13:05 -0500 [thread overview]
Message-ID: <20020510191305.B17142@asooo.flowerfire.com> (raw)
In-Reply-To: <20020509110925.A10839@infradead.org> <Pine.LNX.4.44.0205091502290.490-100000@Expansa.sns.it>
I've been using it quite fruitfully. I think taking it out of 2.4 isn't
a good decision. If 2.4 is supposed to be a stable tree with few major
changes, suddenly taking out functionality that some people rely on
seems inconsistent with that goal. This action would be much more fatal
for the average person who doesn't routinely add feature patchsets to
their kernels, unlike most of us.
However, I am by no means saying khttpd deserves to be in the kernel,
per se. But the decision to remove or not should be a consensus either
way.
Taking it out of 2.5 seems like a very good idea, especially if it's not
being maintained, and especially once TUX2 becomes production-quality,
Replace khttpd with TUX2 in 2.5, says this 'more silent' khttpd user. :)
--
Ken.
ken@irridia.com
On Thu, May 09, 2002 at 03:04:26PM +0200, Luigi Genoni wrote:
|
|
| On Thu, 9 May 2002, Christoph Hellwig wrote:
|
| > On Thu, May 09, 2002 at 02:49:12AM -0700, David S. Miller wrote:
| > > > have little time to fix it. I say pull it from
| > > > 2.4.19-pre9. Marcello, put it out of its misery asap, please...
| > > > it'd time for khttpd to become a standalone patch again.
| > >
| > > Okay, what about the following:
| > >
| > > Are you willing to start being the khttp maintainer?
| > >
| > > I have not seen updates or any attempts at maintaining the
| > > thing in about 2 years. Basically, since it went into the
| > > tree.
| > >
| > > If we aren't changing that situation, we are not removing
| > > the impetus for taking khttpd out of the tree entirely.
| >
| > If khttpd is out-of-tree I volunteer for collecting patches if that
| > is enough for the maintainer status. But I have to admit that I don't
| > really care for it..
| > -
| I do care, but I have no time at all.
| Onestly, I do not think I am the only one using khttpd fruitfully, but I
| tend to suspect that people using it are more silent in front of people
| who do not care for it.
|
|
|
|
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-05-11 0:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 0:28 khttpd rotten? Dan Kegel
2002-05-06 2:14 ` David S. Miller
2002-05-06 2:39 ` Dan Kegel
2002-05-06 10:23 ` Christoph Hellwig
2002-05-06 11:28 ` [PATCH] " Dan Kegel
2002-05-06 17:23 ` Luigi Genoni
2002-05-09 9:49 ` David S. Miller
2002-05-09 10:09 ` Christoph Hellwig
2002-05-09 13:04 ` Luigi Genoni
2002-05-11 0:13 ` Ken Brownfield [this message]
2002-05-06 14:17 ` Tux in main kernel tree? (was khttpd rotten?) Roy Sigurd Karlsbakk
2002-05-06 16:08 ` Andy Carlson
2002-05-06 23:35 ` Anton Blanchard
2002-05-07 14:42 ` Alan Cox
2002-05-07 15:03 ` Andrea Arcangeli
2002-05-07 15:26 ` Alan Cox
2002-05-07 15:38 ` Andrea Arcangeli
2002-05-07 16:02 ` Luigi Genoni
2002-05-06 17:21 ` Dan Kegel
2002-05-06 18:42 ` John Stoffel
2002-05-06 19:07 ` Diego Calleja
2002-05-06 19:18 ` Cort Dougan
2002-05-06 20:47 ` Michael Rothwell
2002-05-09 11:20 ` Appications in kernelspace (was:Tux in main kernel tree?) Anders Peter Fugmann
2002-05-06 21:52 ` Tux in main kernel tree? (was khttpd rotten?) Paul Jakma
2002-05-09 11:28 ` john slee
2002-05-07 3:00 ` J Sloan
2002-05-09 11:40 ` khttpd rotten? john slee
2002-05-09 11:29 ` David S. Miller
2002-05-09 19:30 ` Andrew Morton
2002-05-09 19:35 ` David S. Miller
2002-05-09 19:39 ` Martin Dalecki
2002-05-10 10:20 ` Andi Kleen
2002-05-10 10:49 ` David S. Miller
2002-05-09 20:12 ` Ian Molton
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=20020510191305.B17142@asooo.flowerfire.com \
--to=ken@irridia.com \
--cc=arjanv@redhat.com \
--cc=dank@kegel.com \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=kernel@Expansa.sns.it \
--cc=khttpd-users@alt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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