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:to:references:from:subject:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=wpRW
	pXKo7M3GcHr8L9DDTbzn6tZmVXCsBzl+GJEeOR0fc3no5EbBgrtD5bl9aCa+lqdq
	CQXyRowW2TvZBOMuOc+GldIv1lZpkCjK8YrZ9UuHBLFBKegtFTTrKxKm2lyfY/xV
	9DPV/bwq261xn8+YGh6tAD7/3pr0SaWb84lnaYw=
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:to:references:from:subject:message-id:date
	:mime-version:in-reply-to:content-type; s=default; bh=7R7BzUVSH8
	mFOUNHI6LsMoLWG2k=; b=UL2QzVnCv8D0GfY+O77oB8cqs2/u8cWbTlrJ2wK/pb
	orxMvQgn/6q1saLjipTDRjmSFRAxyJEPJlGKjx7QEGECrE/xJpbJLIIXf1a6TZO4
	kX7PWBE1d+CHajIhKTFGIiHFXO+ltVx4LtNvuQtt6RNPO5O+oLXUoY0Y4jX7bqXc
	Y=
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-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=madison, H*u:x64, H*u:Win64, H*r:sk:20.2019
X-HELO: mail-lf1-f41.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=to:references:from:autocrypt:subject:message-id:date:user-agent         :mime-version:in-reply-to;        bh=z9AO/nQ4A/ljZUBwFOE0FuK8dQjI/5qlwpNKAcyVrMw=;        b=FcEJ2Td1e5gOJrTT55xtKp9HbTV1/KjIDgp+elktZvCNT2sglZVD816PIE1o9VTwWd         NS2X57RTmK17opL6tp76BSQfvEDIjyqnHiEmK6WGo9m1r1NuL/pxOGVSgcQv5ItC9apI         ZHP9KRwWaLm0acE3XumZCZn2r/QnqdmYVroA9zsMLTB1E9zDUcbK9Tvg2s0BMMDQzISU         m4XjzPHwDF/H0ELioobQ3lRCTRlAqBi31y0buGl8r/WCbLX+H5t07lbCgzU9ZlxLFnO3         B8fKS+Q2e98wPEToa6JOoML41unX1eaKvTR1cUpfbz6oWSlHLELI9FYjTKD16mff2xi/         +Csg==
To: cygwin AT cygwin DOT com
References: <dddf240b-0569-1e28-2e53-a5c833e12644 AT gmail DOT com> <CAOTD34ZCHXu0yMNLLhWusM=zq=9S8McHacdwG2DVW+i1R8DQUA AT mail DOT gmail DOT com>
From: LRN <lrn1986 AT gmail DOT com>
Subject: Re: cygwin port of glib
Message-ID: <b91e6a4b-192c-7db2-1f16-8bf335a54607@gmail.com>
Date: Tue, 5 Mar 2019 17:23:32 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <CAOTD34ZCHXu0yMNLLhWusM=zq=9S8McHacdwG2DVW+i1R8DQUA@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rZaYRsf7wErWxgitsqWfwtZffJiapkfoo"
X-IsSubscribed: yes

--rZaYRsf7wErWxgitsqWfwtZffJiapkfoo
Content-Type: multipart/mixed; boundary="nEkp1y1Y5n76sMkUvD9X4yJBSElG7BQ03";
 protected-headers="v1"
From: LRN <lrn1986 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <b91e6a4b-192c-7db2-1f16-8bf335a54607 AT gmail DOT com>
Subject: Re: cygwin port of glib


--nEkp1y1Y5n76sMkUvD9X4yJBSElG7BQ03
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 05.03.2019 17:07, E. Madison Bray wrote:
> On Sun, Mar 3, 2019 at 11:07 AM LRN wrote:
>>
>> Looking at cygwin glib source package, i see a lot of downstream patches
>> applied to glib over the years (there are no dates, but the versions ran=
ge from
>> 2.34.3 to 2.50 - that might be as early as 2012 and as late as 2017) to =
make it
>> work correctly on cygwin.
>>
>> Why are these not upstream (considering the fact that glib does have some
>> cygwin-specific code - clearly it's not because glib doesn't *want* cygw=
in
>> compatibility)?
>>
> but in
> this case I would suggest that, if you care enough to do it, you
> should offer to upstream that they accept some/all of those patches,
> as in most cases they may not even be aware it exists. My guess is
> that whoever is maintaining the glib package for Cygwin

That would probably be Yaakov Selkowitz[0].

> either doesn't
> know glib well enough to be able to advocate effectively for those
> patches, or doesn't care enough to.
>=20
> If they're clean, worthwhile patches then I absolutely think you
> should get them integrated upstream if at all possible--that's almost
> always preferable.

Okay, i'll see what i can do.

[0]: https://github.com/cygwinports/glib2.0/commits/master


--nEkp1y1Y5n76sMkUvD9X4yJBSElG7BQ03--

--rZaYRsf7wErWxgitsqWfwtZffJiapkfoo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4MWzR43wYaAzEA49ja3pJ2dZunQFAlx+hmQACgkQja3pJ2dZ
unQM7Q/+K9hxtA2GjIJdqedp4aHx22sj71joYIIa+JPN2GCS3jot1S8v5WiW4jUE
L+hIcQNOGDzKxMTx7bQ5Q0125/7S6yFoSnxibw1PT0BqXYl56KKk695Nb9FpK7t5
yFafi3DcLlE+TwRb4UGHJyPm6PXvSlllhQo60unJqIGwZX1brcHkx8uaKLXD6MaZ
Sjn5d9YwdOOS4gPqWV5yQSvByPxzaeFwBQX4GX61Oll6SemrXwpje+PKVpqsU9e1
i5Kt8h79WbEltFyWRn6y0o3aUe3XTYrXo8CoJ6H7gSdsUxy5ucjmjaTli0kbSCRV
32TzbiyDsb1WstkUUEnIomquLDFosN1HpWDx8GNL3/AQ8vLCDr2QdOn7WuNakusw
y6SRrveVmLV1PxCHd6zUWHys7w5BCY2U0fAvRNqPKka+RpH7Tydi2KLgyd0VFdf3
Gw9uNprTwJJAZwqEGsavSdtuE+wVLnT7bPEi3QmRQ7rxURvwWGWrQFtzxBJ3tDoL
XlqMLXCZHsjw2N77vD5wC3CFwbR3DV8WTA4QV/kDHan5rcShlBjNcfwp4+gUua07
0ig/cCKNi3QOLzYHhixdWaQP1ANQaNDvlkiQUMg0jqcaEknVN9ZJvgxAyDmorLlI
SBySgaH3BhfztxzfXQPAnrQw7wlv3wur/ENo7tFrIYxRTLwfZPI=
=SR1i
-----END PGP SIGNATURE-----

--rZaYRsf7wErWxgitsqWfwtZffJiapkfoo--