From dev-return-8999-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Sat Nov 05 20:27:33 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 35051 invoked from network); 5 Nov 2005 20:27:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Nov 2005 20:27:32 -0000 Received: (qmail 8290 invoked by uid 500); 5 Nov 2005 20:27:31 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 8246 invoked by uid 500); 5 Nov 2005 20:27:30 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 8235 invoked by uid 99); 5 Nov 2005 20:27:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Nov 2005 12:27:30 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates 205.152.59.65 as permitted sender) Received: from [205.152.59.65] (HELO imf17aec.mail.bellsouth.net) (205.152.59.65) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Nov 2005 12:27:24 -0800 Received: from ibm57aec.bellsouth.net ([65.80.200.112]) by imf17aec.mail.bellsouth.net with ESMTP id <20051105202708.KIRE2217.imf17aec.mail.bellsouth.net@ibm57aec.bellsouth.net> for ; Sat, 5 Nov 2005 15:27:08 -0500 Received: from [172.16.1.39] (really [65.80.200.112]) by ibm57aec.bellsouth.net with ESMTP id <20051105202708.QAXO20717.ibm57aec.bellsouth.net@[172.16.1.39]> for ; Sat, 5 Nov 2005 15:27:08 -0500 Message-ID: <436D159B.1040002@bellsouth.net> Date: Sat, 05 Nov 2005 15:27:07 -0500 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@directory.apache.org Subject: [SVN] Cleaning up before the restructuring. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi guys, Just as a heads up I cleaned up some obsolete tags laying around. In the tags directories of various projects I removed obsolete tags only and referenced them with a readme.txt such as this one: readme.txt in directory/shared/ldap/tags ------------------------- Some significant tags have been deleted but may be resuscitated or checked out by copying them back or exporting them using a revision number. Here we list those tags within the repository for future reference. This is done to keep the project root checkout lean, so only those branches in use should be present. tag: internal-release-0.9.2 deleted on: Thu Oct 27 2005 delete rev: 329033 resuscitate: svn cp -r 329032 https://svn.apache.org/repos/asf/directory/shared/l dap/tags/internal-release-0.9.2 internal-release-0.9.2 tag: internal-release-0.9.1 deleted on: Thu Oct 27 2005 delete rev: 329033 ds: svn cp -r 329032 https://svn.apache.org/repos/asf/directory/shared/l dap/tags/internal-release-0.9.1 internal-release-0.9.1 ... --------------------------- The tags in use have been left there. For example in MINA everything below release-0.8.0 is now obsolete. Hence there was no reason to keep internal-release-0.7, release-0.7.1, release-0.7.2, release-0.7.3 and release-0.7.4 hanging around. Users that would like these can retrieve them by resuscitating the tag using the svn command with revision number in the readme.txt. Note that we won't need this mechanism anymore after we goto the flat structure with one releases and one trunk. I'll be glad to see this mechanism gone. However I started cleaning this up using the old mechanism so we have less work to do to get to the new SVN layout. Under directory/releases we will not have to delete old tags because the checkout behavior will change. However for these releases that used the old structure we might want to put them under an 'old-releases' directory within releases. Anyhow we can resuscitate the old tags anytime or just copy the readme under old-releases. Alex