Return-Path: Delivered-To: apmail-directory-mina-dev-archive@locus.apache.org Received: (qmail 5508 invoked from network); 2 Nov 2006 14:59:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Nov 2006 14:59:30 -0000 Received: (qmail 77740 invoked by uid 500); 2 Nov 2006 14:59:41 -0000 Delivered-To: apmail-directory-mina-dev-archive@directory.apache.org Received: (qmail 77726 invoked by uid 500); 2 Nov 2006 14:59:41 -0000 Mailing-List: contact mina-dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mina-dev@directory.apache.org Delivered-To: mailing list mina-dev@directory.apache.org Received: (qmail 77711 invoked by uid 99); 2 Nov 2006 14:59:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 06:59:41 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of elihusmails@gmail.com designates 64.233.162.195 as permitted sender) Received: from [64.233.162.195] (HELO nz-out-0102.google.com) (64.233.162.195) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 06:59:26 -0800 Received: by nz-out-0102.google.com with SMTP id z3so122868nzf for ; Thu, 02 Nov 2006 06:59:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XB2RcfkQzxoftAQqdIpbIgvh3fvcZCp5EIk14zgyQx22ZUNgoqEo9/BPwCHS3rWyEy28zc40VB3MmcZpwtNbUOpUrkdu9NR3uKZkOEErRWqmJGck0ZYsWVCH/4G98Qe8zqh65mtTYMoEGQcgj/iYO7wu2heVkB5oHyuwdA0MZ/s= Received: by 10.65.43.17 with SMTP id v17mr899495qbj.1162479545650; Thu, 02 Nov 2006 06:59:05 -0800 (PST) Received: by 10.65.103.10 with HTTP; Thu, 2 Nov 2006 06:59:05 -0800 (PST) Message-ID: <9f066ee90611020659j244496e5le8560eca36b8f530@mail.gmail.com> Date: Thu, 2 Nov 2006 09:59:05 -0500 From: "Mark Webb" To: mina-dev@directory.apache.org Subject: Re: New to SVN In-Reply-To: <7E664C9A7DB0A942AB7AF0260D99AB83A83E89@FL67EXM02.gddsi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7E664C9A7DB0A942AB7AF0260D99AB83A83E89@FL67EXM02.gddsi.com> X-Virus-Checked: Checked by ClamAV on apache.org You are right on. trunk is analogous to head in CVS, and branches are, the branches. Here is a link to the subversion manual: http://svnbook.red-bean.com/ On 11/2/06, Newcomb, Michael-P57487 wrote: > I'm new to SVN, but am familiar with CVS. So please bear with me as I > will probably ask some dumb questions... > > When viewing http://svn.apache.org/viewvc/directory: > > I see branches, releases, and trunks... > > trunks/mina I assume is analagous to HEAD? > > releases/mina seems to have all the versioned releases of MINA. So, do > you check out stuff under the releases/mina area? Or do you work in > another area and when you want to release 1.0.1, it gets put into > releases/mina? > > branches/mina seems to have the major version numbers, but what exactly > is this for? Are each of these branches used to continue development on > the 0.8 and 1.0 branches? > > Is trunks/mina 1.1? > Is branches/mina/1.0 1.0.1? > > Can someone help me understand the cm strategy? > > Thanks, > Michael > > > > >