Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 30 Mar 2003 18:09:42 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: CVS Tags for 1.3.22 [FAQ alert] Message-ID: <20030330230942.GE24994@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030330225650 DOT GD24994 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Sun, Mar 30, 2003 at 05:59:53PM -0500, Igor Pechtchanski wrote: >On Sun, 30 Mar 2003, Christopher Faylor wrote: >> The only branches that are actively being worked on are my branch and >> the trunk. There is nothing happening on any other branch. >> cgf > >Does this mean that all further Cygwin releases will be done from the >trunk? For the most part, all cygwin releases have been made from the trunk. It is only in rare cases that a branch is set up and that's usually when destabilizing changes were made to the trunk but show stopper bugs are found in a release. I sometimes set up a tag for my own use but I have almost never tagged enough things in the repository to make a tag useful for going back to a previous release. David, can we add something like this to the FAQ. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/