Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 82255 invoked by uid 500); 6 Aug 2002 01:16:16 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 82240 invoked from network); 6 Aug 2002 01:16:16 -0000 Date: Mon, 5 Aug 2002 18:16:22 -0700 From: Sander van Zoest To: dev@httpd.apache.org Subject: Re: [PATCH] improve config dir processing Message-ID: <20020805181621.F65500@escher.san.yahoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from joshua@slive.ca on Tue, May 28, 2002 at 12:20:10PM -0700 Organization: Yahoo!, Inc. X-Accept-Language: en-us, en, nl, be, fr, de X-PGP-Key-URL: http://sander.vanzoest.com/pgp-public-key.asc X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, May 28, 2002 at 12:20:10PM -0700, Joshua Slive wrote: > OK. I'm convinced. At least three people have said they use this > extensively, so we should continue to support it. Why don't we just keep > the existing behavior and add "Include dir/*.conf" as an option. We can > assume that people who are using recursively included directories are > smart enough that they can avoid the backup problem on their own. Did we ever add this functionality? If not, I would like to see this added and I am willing provide a patch for 1.3 and 2.0 to add the "Include dir/*.conf" functionality as described above. Any objections? -- Sander van Zoest +1 (619) 881-3000 Yahoo!, Inc. sander@yahoo-inc.com