This is the mail archive of the cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: self hosting + nightly snapshots
- To: andrewd@axonet.com.au
- Subject: Re: self hosting + nightly snapshots
- From: DJ Delorie <dj@delorie.com>
- Date: Wed, 17 Feb 1999 21:59:28 -0500
- CC: cygwin-developers@sourceware.cygnus.com
- Delivered-To: listarch-cygwin-developers@sourceware.cygnus.com
- Delivered-To: mailing list cygwin-developers@sourceware.cygnus.com
- In-reply-to: <91A8FD196436D1118EC2006008186C961326A0@server1.axonet.com.au>(message from Andrew Dalgleish on Thu, 4 Feb 1999 16:12:37 +1100)
- Mailing-List: contact cygwin-developers-help@sourceware.cygnus.com; run by ezmlm
- References: <91A8FD196436D1118EC2006008186C961326A0@server1.axonet.com.au>
- Sender: cygwin-developers-owner@sourceware.cygnus.com
> 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.
There is *always* a risk that the snapshots won't build. If you
expect otherwise, please change your expectations.