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: Sat, 5 Apr 2003 19:45:42 +0200 (CEST) From: cm1 AT mercury DOT muc DOT de To: cygwin AT cygwin DOT com Subject: Re: CVS Tags for 1.3.22 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks! I downloaded the snapshot and played around with the dates and tags until I had everything matching. BTW, I did use the branch dontuse-21 for the cygwin directory because it matched the snapshot precisely at the time I ran cvs update. This will change as new updates are checked in, of course, and require additional time stamps.... It would be nice to have official tags but I assume this has been discussed in the past and I don't want to start a new discussion. Thanks, --Christian On Sun, 30 Mar 2003, Igor Pechtchanski wrote: > On Sun, 30 Mar 2003 cm1 AT mercury DOT muc DOT de wrote: > > > Hi, > > > > 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"? > > > > Thanks, > > --Christian > > Christian, > > 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. > Igor > -- 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/