Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 55699 invoked from network); 21 Dec 2006 11:18:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Dec 2006 11:18:48 -0000 Received: (qmail 24574 invoked by uid 500); 21 Dec 2006 11:18:46 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 24498 invoked by uid 500); 21 Dec 2006 11:18:46 -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: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 24470 invoked by uid 99); 21 Dec 2006 11:18:46 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 03:18:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [212.227.126.173] (HELO moutng.kundenserver.de) (212.227.126.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 03:18:30 -0800 Received: from [212.227.126.202] (helo=mrvnet.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1GxLw9-00048L-00 for dev@httpd.apache.org; Thu, 21 Dec 2006 12:18:09 +0100 Received: from [172.23.1.26] (helo=xchgsmtp.exchange.xchg) by mrvnet.kundenserver.de with smtp (Exim 3.35 #1) id 1GxLw9-0007bg-00 for dev@httpd.apache.org; Thu, 21 Dec 2006 12:18:09 +0100 Received: from mapibe05.exchange.xchg ([172.23.1.25]) by xchgsmtp.exchange.xchg with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Dec 2006 12:18:09 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Apache BUG: 36495 : ajp_proxy_connect_backend failure Date: Thu, 21 Dec 2006 12:18:05 +0100 Message-ID: In-Reply-To: <458A4737.40505@rowe-clan.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Apache BUG: 36495 : ajp_proxy_connect_backend failure thread-index: Acck2vkRrQ3ONe1oQMSePzuXX4k6zAAE0KtA From: "Trent Nelson" To: X-OriginalArrivalTime: 21 Dec 2006 11:18:09.0647 (UTC) FILETIME=[B21027F0:01C724F1] X-Provags-ID: kundenserver.de abuse@kundenserver.de ident:@172.23.1.26 X-Virus-Checked: Checked by ClamAV on apache.org > > I find that svn externals can provide a useful alternative to the > > approach you've mentioned: >=20 > Externals are evil. >=20 > They are *very* prone to mis-tagging. A tag with externals pointing > back to another leaf of a trunk are WORTHLESS. Several projects have > been guilty of this. I'd certainly agree that *tagging* a structure that contains externals pointing to other trunk branches is a recipe for disaster. As long as you don't do this, they can be very useful, even if your entire externals definition is composed of tagged/read-only branches: http://svn.apache.org/repos/asf/httpd/httpd/views/2.2.3 svn:externals: src/ http://svn.apache.org/repos/asf/httpd/httpd/tags/2.2.3 src/srclib/apr http://svn.apache.org/repos/asf/apr/apr/tags/1.2.8 src/srclib/apr-util http://svn.apache.org/repos/asf/apr/apr-util/tags/1.2.8 src/srclib/apr-iconv http://svn.apache.org/repos/asf/apr/apr-iconv/tags/1.1.1 Thus, I could check out the exact source used to build 2.2.3 via: svn co http://svn.apache.org/repos/asf/httpd/httpd/views/2.2.3 I'd personally prefer this sort of an approach to, say, relying on the source tars that are manually rolled at release time. Trent.