Delivered-To: listarch-cygwin-developers AT sourceware DOT cygnus DOT com Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <91A8FD196436D1118EC2006008186C9613BFE8@server1.axonet.com.au> From: Andrew Dalgleish To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: RE: self hosting + nightly snapshots Date: Thu, 18 Feb 1999 14:30:22 +1100 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) > -----Original Message----- > From: DJ Delorie [SMTP:dj AT delorie DOT com] > Sent: 1999 February 18, Thursday 13:59 > To: Andrew Dalgleish > Cc: cygwin-developers AT sourceware DOT cygnus DOT com > Subject: Re: self hosting + nightly snapshots > > > > How is it determined whether or not to put a newlib snapshot up? > > newlib snapshots are included no more than once every five days. This > is mostly to reduce disk space needs. As newlib doesn't change that > often, this is a calculated risk. When it happens, we can either post > a suitable patch, or you can wait a few days for a newlib snapshot to > show up. > > > Is this done automatically? > > Yes. The entire snapshot system is 100% automated and unattended. [Andrew Dalgleish] Sounds good. Is there any chance of getting md5sums or similar? > There is *always* a risk that the snapshots won't build. If you > expect otherwise, please change your expectations. [Andrew Dalgleish] Done. I am the software build manager for Axon Instruments, so I sympathize :-)