X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=w88H
	j3AdYfvIMhSvv4akcVJtdfrykL/FcRLvPDJYvRpwJ5RCbW2m78vmv6NEd6J6mFXn
	R4jpKygU24rKwVx59a90S4G/9v9rbtrESxIyswX7LZp+UaTjtgWz3UsP2gLjEGFy
	JP0hi5u9wkIZfPDDrZGIVwVoVY+SRvxWCeEDx4Y=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=vYG4pt2Evr
	5YxwDY5djTRv7GmsY=; b=EC+t1aUeYTjbZMIJUB9BlWVLsREq9ndA7/jzRAArjn
	8HiaPN1dXeP+dhG74AB6f6BlRo4sMH95xIu44tcuctxN4f+UnNLWzyFNuRWCatpa
	+Bp5tYyTmu2rS0V3fXXQCCnjloupAMS+jOQUBK0+Osd/io1ynRQWrZysQg54fiii
	0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.3.2 spammy=sees, H*f:sk:wg AT mail, H*i:sk:wg AT mail, H*i:CALd
X-Spam-User: qpsmtpd, 2 recipients
X-HELO: calimero.vinschen.de
Date: Tue, 28 Jun 2016 13:44:50 +0200
From: Corinna Vinschen <vinschen AT redhat DOT com>
To: Qian Hong <fracting AT gmail DOT com>
Cc: cygwin <cygwin AT cygwin DOT com>, newlib AT sourceware DOT org
Subject: Re: [PATCH] Add continuous integration build configuration for Cygwin
Message-ID: <20160628114450.GC23625@calimero.vinschen.de>
Mail-Followup-To: Qian Hong <fracting AT gmail DOT com>,	cygwin <cygwin AT cygwin DOT com>, newlib AT sourceware DOT org
References: <CALd+sZTkJR9dP0O_DiR6F6-4RjgmzVt5b2vW2-4uUz2J6oC+wg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="tqI+Z3u+9OQ7kwn0"
Content-Disposition: inline
In-Reply-To: <CALd+sZTkJR9dP0O_DiR6F6-4RjgmzVt5b2vW2-4uUz2J6oC+wg@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)

--tqI+Z3u+9OQ7kwn0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun 28 17:40, Qian Hong wrote:
> Hi,
>=20
> I'd like to volunteer to maintain a(nother) continuous integration
> build for Cygwin. Thanks to Jon Turney we recently setup an Appveyor
> build for Cygwin on Windows. This time I'm proposing a Tea CI build
> for Cygwin on Wine.
>=20
> Attached is the build configuration, which includes three parts:
> The "stage1" part build Cygwin runtime on Cygwin (on Wine), the "test"
> part copy the new cygwin1.dll to override the current cygwin1.dll, and
> do some simple test to verify the new runtime dll starts correctly,
> the "stage2" part rebuild Cygwin using the newly built cygwin1.dll
> environment as a self test.
>=20
> Here are some examples for build results:
> - Tea CI detects build failure of cygwin:
> https://tea-ci.org/fracting/cygwin/112
> - Tea CI detects runtime failure of new cygwin1.dll:
> https://tea-ci.org/fracting/cygwin/110
>=20
> We've successfully used Tea CI to detect build failure and runtime
> failure before, which were already reported to upstream, I hope to
> upstream this build configuration so we could detect those failures
> even earlier, and I'll volunteer to maintain the build script and
> monitor the build results. Please consider the patch, let me know
> anything else I can do.
>=20
> Regarding the new procedure for code contributions to the Cygwin
> sources, since I've submitted patches to Cygwin before with Cygwin
> Copyright Assignment signed, I think I'm fine here ;) But anyway I'm
> happy to declare I provide my patches to Cygwin source under the
> 2-clause BSD license as
> https://cygwin.com/ml/cygwin-announce/2016-06/msg00050.html.

No worries here for toplevel or newlib.

I applied this change for now.  If somebody on the newlib list sees any
problem with it, please explain.


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer
Red Hat

--tqI+Z3u+9OQ7kwn0
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXcmMyAAoJEPU2Bp2uRE+g79YP/3AlLgh3qHu4MpKAKUpXp4ZN
rrkwxXmbbaAOoXMc3NHWO/RPuHuFriF2B7QHOKoF2xhefAOI+s4u2g6MgZjMlSSf
xWUgvPjDXik56Qkr2ZL3YkmjTxQtLEl2HLF4TOvaicnNKlLRPh/URi48PxK2e4rr
QpgO3ULU4IAb1Zuo2qds9WtAjVhRMUJ53eE3m8hg+CGjRxWxN32BqAEEoLu3VRTT
/4ARjy5ShfJnQlRP6SEdY57j4Y9K/Zd/K+O3ElSXDjgAcTFctTl81oI05Waa4BBe
g+uAdYJPLG10XMPL9Tz00XIJCevAxmmn5WKtzjsu6vqWGdQ03quIGThkalqBl4V5
NYRf/twkQEpA6i9doFmo3BwnEQjMqBrbgsEvRWrI086hWcC1LR6ox83tNsRw9c/D
paGGTFyJ7njFnOUifabPqp2cJsraKAyiOyt4Yhpwih1OcOK3dN6Cgt4rfaJlDCha
u9HtQa56UBfoQsGnghUcvM+W7m1k3FX8JJfGAH+9SMHQ50BUJEen6Rz3+F/PvWpe
nr+XiUKpCUX4GV06M83dHUNHD0/VjTslS37heacVMorS0iAUYCNkPfiPZswtVNzR
ixF9JIzdG7TMm7RSQmQdZU3PeBmj9edIJlJ2QhZlEJ9KyIIzODAfuVqN3kPJFtwU
l3lyrpINZx694QNcbyVi
=r1rL
-----END PGP SIGNATURE-----

--tqI+Z3u+9OQ7kwn0--