X-Spam-Check-By: sourceware.org
Message-ID: <cb51e2e0601262138s5e36bba4w864f9dfdc9992982@mail.gmail.com>
Date: Thu, 26 Jan 2006 21:38:10 -0800
From: Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Building Cygwin from CVS
In-Reply-To: <20060126191421.GC8318@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <43CE88C6 DOT 3070009 AT hones DOT org DOT uk> 	 <cb51e2e0601192053lb0a0ba7i4284a2cd57e6c9e0 AT mail DOT gmail DOT com> 	 <43D12B2C DOT 23DD92C8 AT dessent DOT net> 	 <cb51e2e0601252041tf586afdl9cc2e32fe669e163 AT mail DOT gmail DOT com> 	 <20060126091207 DOT GS8318 AT calimero DOT vinschen DOT de> 	 <20060126184423 DOT GA304 AT trixie DOT casa DOT cgf DOT cx> 	 <20060126191421 DOT GC8318 AT calimero DOT vinschen DOT de>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k0R5cIBd030379

On 1/26/06, Corinna Vinschen wrote:
> On Jan 26 13:44, Christopher Faylor wrote:
> > On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote:
> > >On Jan 25 20:41, Joshua Daniel Franklin wrote:
> > >>I've added this info to
> > >>http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin
> > >>and I'd like to put it in a winsup/README file but didn't want to touch
> > >>the top-level without some discussion.  Does that sound OK to do?
> > >
> > >Yes, we can add a winsup/README if you want to do this.  Would you mind
> > >to create a winsup README which basically follows the layout of the
> > >newlib README?  That would be cool.
> >
> > My preference would be for build instructions in only one place, I guess
> > that would mean that they should be in the FAQ since that is the most visible
> > place.
>
> Good argument.
>
> > So, I'd like the README to basically just have a URL for the cygwin web site.
> > And, this README should not be installed.
>
> Right, I agree.

OK, the full text of winsup/README is now:


THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Cygwin documentation is available on the net at http://cygwin.com
You might especially be interested in

http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/