Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 30 Mar 2003 17:56:50 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: CVS Tags for 1.3.22 Message-ID: <20030330225650.GD24994@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: 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:52:59PM -0500, Igor Pechtchanski wrote: >On Sun, 30 Mar 2003 cm1@mercury.muc.de wrote: >> I couldn't find any CVS tags to build Cygwin 1.3.22 from source; the best >> I could find was the branch "dontuse-21" which doesn't seem to be correct. >> Is there some documentation around this somewhere on the Cygwin web pages? >> If not, could someone let me know which tags/time stamps to use? I don't >> want to get the 64-bit file offsets which are being worked on in the trunc >> version by accident.... >> >> Furthermore, is there some documentation about the tags to use for the >> support libs such as "newlib"? > >This issue has been raised before. The tags are for cgf's convenience >only. There are no guarantees that they would correspond to any >particular version of the release. One way of figuring out the CVS >timestamp to check out is downloading the corresponding source package and >looking at its timestamps... I'm not sure how the timestamps will now >interact with the development on separate branches, though. Other ways >may be suggested by people here. The only branches that are actively being worked on are my branch and the trunk. There is nothing happening on any other branch. 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/