Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Date: Sat, 16 Oct 2004 13:30:37 +0100 (BST)
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
Subject: Re: [RFC] Patch for mod_log_config to allow conditioning on status
 code
In-Reply-To: <20041016081920.GA7296@netspace.org>
Message-ID: <Pine.LNX.4.53.0410161323410.1042@hugin.webthing.com>
References: <416F93BC.76A4FB3E@skopos.be>
 <Pine.LNX.4.53.0410151828090.7420@hugin.webthing.com>
 <20041016020256.GA32537@netspace.org> <417083EB.50409@force-elite.com>
 <20041016081920.GA7296@netspace.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 16 Oct 2004, Glenn Strauss wrote:

> I don't want to discourage Luc, but there's a steep uphill battle
> to getting anything into Apache 1.3.

Of course.  Apache 1.3 is an old, legacy application, and vastly less
capable than current versions.  It's still maintained, but noone is in
the business of adding new *features*.

2.1 is where interesting things happen, while 2.0 is intermediate: new
features may be added, but stability and binary-compatibility are more
important.  I might review and incorporate a third-party patch for 2.x,
but certainly wouldn't for 1.x unless someone was paying.

> diff -ruN apache_1.3.31/src/main/http_log.c apache_1.3.31-new/src/main/http_log.c
> --- apache_1.3.31/src/main/http_log.c   2004-02-16 17:29:33.000000000 -0500
> +++ apache_1.3.31-new/src/main/http_log.c       2004-05-24 12:26:06.000000000 -0400

Bugzilla is a good place for patches like that.  People who want it can
help themselves, without compromising stability.

-- 
Nick Kew