Return-Path: Delivered-To: apmail-perl-dev-archive@www.apache.org Received: (qmail 87394 invoked from network); 21 Nov 2004 18:52:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Nov 2004 18:52:53 -0000 Received: (qmail 53552 invoked by uid 500); 21 Nov 2004 18:52:52 -0000 Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 53533 invoked by uid 500); 21 Nov 2004 18:52:51 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 53510 invoked by uid 99); 21 Nov 2004 18:52:51 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [216.254.0.202] (HELO mail2.speakeasy.net) (216.254.0.202) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 21 Nov 2004 10:52:48 -0800 Received: (qmail 29633 invoked from network); 21 Nov 2004 18:52:42 -0000 Received: from dsl093-038-250.pdx1.dsl.speakeasy.net (HELO [192.168.1.22]) (davidw@[66.93.38.250]) (envelope-sender ) by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Nov 2004 18:52:42 -0000 In-Reply-To: <41A0CBB3.1050607@stason.org> References: <41A0CBB3.1050607@stason.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8669A74A-3BEE-11D9-BC8B-000A95B9602E@kineticode.com> Content-Transfer-Encoding: 7bit Cc: mod_perl Dev From: David Wheeler Subject: Re: can someone explain the new modperl svn layout? Date: Sun, 21 Nov 2004 10:52:42 -0800 To: Stas Bekman X-Mailer: Apple Mail (2.619) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Nov 21, 2004, at 9:09 AM, Stas Bekman wrote: > It should be something like (1): > > http://svn.apache.org/viewcvs.cgi/perl/modperl-docs > http://svn.apache.org/viewcvs.cgi/perl/modperl-2.0 > http://svn.apache.org/viewcvs.cgi/perl/modperl-1.0 > > If we are planning to do a different nesting to accomodate other > projects it could be (2): > > http://svn.apache.org/viewcvs.cgi/perl/modperl/docs > http://svn.apache.org/viewcvs.cgi/perl/modperl/2.0 > http://svn.apache.org/viewcvs.cgi/perl/modperl/1.0 > http://svn.apache.org/viewcvs.cgi/perl/embperl/1.0 > http://svn.apache.org/viewcvs.cgi/perl/embperl/2.0 I agree that these would be a lot more clear and meaningful, although you *should* have a "trunk" directory in there somewhere. I like these: https://svn.apache.org/trunk/perl/modperl/docs https://svn.apache.org/trunk/perl/modperl/2.x https://svn.apache.org/trunk/perl/modperl/1.x https://svn.apache.org/trunk/perl/embperl/1.x https://svn.apache.org/trunk/perl/embperl/2.x But this is also okay: https://svn.apache.org/perl/modperl/docs/trunk https://svn.apache.org/perl/modperl/2.x/trunk https://svn.apache.org/perl/modperl/1.x/trunk https://svn.apache.org/perl/embperl/1.x/trunk https://svn.apache.org/perl/embperl/2.x/trunk Of course, whenever you crete a branch, it would have to look something like this: https://svn.apache.org/perl/modperl/2.x/branches/branch_name Likewise for tags, it would have to be: https://svn.apache.org/perl/modperl/2.x/tags/tag_name For the first example they would have to be like this: https://svn.apache.org/branches/branch_name/perl/modperl/2.x https://svn.apache.org/tags/tags_name/perl/modperl/2.x Which I have to say, given the multiproject nature of the Apache svn installation, probably makes less sense. More on repository layout and the ideas behind it is documented here: http://svnbook.red-bean.com/en/1.1/ch04s07.html#svn-ch-4-sect-7.1 Regards, David --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org