Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Sun, 30 Mar 2003 17:59:53 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: CVS Tags for 1.3.22
In-Reply-To: <20030330225650.GD24994@redhat.com>
Message-ID: <Pine.GSO.4.44.0303301758150.21921-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 30 Mar 2003, Christopher Faylor wrote:

> On Sun, Mar 30, 2003 at 05:52:59PM -0500, Igor Pechtchanski wrote:
> >On Sun, 30 Mar 2003 cm1 AT mercury DOT muc DOT 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

Does this mean that all further Cygwin releases will be done from the
trunk?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
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/