Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Wed, 10 Apr 2002 13:24:44 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: [ANN] updated: apache-1.3.24-1 Message-ID: <20020410172444.GF21488@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <3CB03249 DOT 92BE4405 AT wapme-systems DOT de> <3CB41D01 DOT C683A3D AT wapme-systems DOT de> <20020410131547 DOT M1127 AT cygbert DOT vinschen DOT de> <3CB4627D DOT 5050406 AT ece DOT gatech DOT edu> <3CB4708D DOT 67D8819B AT wapme-systems DOT de> <3CB473AD DOT 40005 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CB473AD.40005@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Wed, Apr 10, 2002 at 01:17:33PM -0400, Charles Wilson wrote: >Stipe Tolj wrote: > >>Ok, should I CC to cygwin@ by hand now?! > > >No need to panic?! > >For the short term, yes. Once Chris fixes the gateway (or gets >cygwin-announce out of spamassisin's black hole), then you can stop. A practical person would probably still send email to cygwin-announce, wait to see if it shows up on cygwin in an hour or so, and if not, send the email to cygwin AT cygwin. I won't know if I've fixed the problem until the next announcement comes in. cgf