DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=WtnWxa
	CDmGvaXj+v4X37Xl1lO5YJDbW68CG+CUznkFiko+0ltiB+EP1DgRuUP+L0nmjkSK
	P4/vykIDL15nBVx400bmmhyOzP5H6moZLw6mSh1YyEzz9Ya83iSuYVbtZg05h27o
	3M7yiqbzQMddaMKcnQiOyxySX0SHEQtPWkT44=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <517C79B5.2040000@gmail.com>
Date: Sun, 28 Apr 2013 09:21:57 +0800
From: JonY <10walls AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Attn: JonY -- Re: Bug in ddk headers when used from cygwin
References: <51625CAE DOT 2030703 AT cwilson DOT fastmail DOT fm> <20130408074801 DOT GA10199 AT calimero DOT vinschen DOT de> <51630442 DOT 4080805 AT cwilson DOT fastmail DOT fm> <20130409091609 DOT GI10126 AT calimero DOT vinschen DOT de> <51641548 DOT 2060700 AT cwilson DOT fastmail DOT fm> <20130409135842 DOT GC15271 AT calimero DOT vinschen DOT de> <517ADF9C DOT 4000606 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <517ADF9C.4000606@cwilson.fastmail.fm>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2SSSAXVHCOTPUMRFGVJOB"

------enig2SSSAXVHCOTPUMRFGVJOB
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/27/2013 04:12, Charles Wilson wrote:
> Any thoughts on this -- the idea that the cygwin (and cygwin64) package of
>=20
>    w32api-headers
>    w32api-runtime
>=20
> should be stripped of any ddk-related items, as they can't actually be
> mixed with the usable-from-cygwin user mode w32 items?
>=20
> Arguably this might break some things -- such as the (old version of)
> csih/getVolInfo -- but they are actually already broken, with the (bug
> or compile failure) just waiting to be exposed.

Got it, will do that for the next refresh.


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)

iQIcBAEBAgAGBQJRfHm+AAoJEHE7X+KcFF1FnT8QAJDHFvAHGTFaMcZbt1lmQZrP
i4JRoTx2D8dnv9l7V7bCh2o1Ll9s45JIFJQZCLBHQDXhKdIHTAwqtYGRorEWrIqn
/HG9BcYSzYe9zJtdUaF/NTGBiNHYWDZznXrAuWLZdUMofzORQnjMFtzEw9ewN5cx
a01lO2h0x7GRZMp7B8NPWBDh6TS4drpgepBuVViYvEbgb3smqJzZLdnvsgKUU4ZU
xlXaUsYj1fWqXzOZyGG/MLZmM/oTfh7ttoYGTWPgqZCtrsIFV+vHqgsVOSry2UkC
8SAXpqffdWVKU23vUhzyDB8oB4AzTxjxLLDGgDrqYoWwNxnGi9LpFepgldaIFTtn
F9RdoSs5ve3n5Aqs0L/41XT0v+FTYr8ALUGu4r5fVrP6icg572LF1bXjKwrNpXGk
6vHB1hgY4142kKplRFTs8D0bWV88modmH/+E1gywAT0wu7DyJkbWLvD6Ep1F4aNf
i3mB5cMuVDn+pzw4E2bXjUCc8ROK2h4P3hqkJs8rGjhc1k0FqG3Xn6Mz5AjlybcA
Kh2B00doNR4Q1ks4/UEnfXy7DlCE7ZEi99yHlExoNauN2FYyAZaKcDLePClLUsB4
mb/YT67hitBLedVy89JYBSIrKC864No7xwpeYBJ8yeT3ucIJ5K1mqpQnVHf8kcnj
8wP+see/oULGsyZXQysV
=ggQC
-----END PGP SIGNATURE-----

------enig2SSSAXVHCOTPUMRFGVJOB--