cvs.gedasymbols.org/archives/browse.cgi | search |
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 |
Date: | Wed, 17 Feb 1999 21:59:28 -0500 |
Message-Id: | <199902180259.VAA20279@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | andrewd AT axonet DOT com DOT au |
CC: | cygwin-developers AT sourceware DOT cygnus DOT com |
In-reply-to: | <91A8FD196436D1118EC2006008186C961326A0@server1.axonet.com.au> |
(message from Andrew Dalgleish on Thu, 4 Feb 1999 16:12:37 +1100) | |
Subject: | Re: self hosting + nightly snapshots |
References: | <91A8FD196436D1118EC2006008186C961326A0 AT server1 DOT axonet DOT com DOT au> |
> 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.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |