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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=JovnGXJatepq/HQg
	xoHqH8Wwx/tBzojhZYNTv3RdpwCiqWozdK27n18POhrpIWfRw7UJzfi7Pek08llg
	2mgXT7L+EUvKvYcXfKj42SRSnKiFeU/xB/m3LJHtM/uw2V4ohBXlEYcOg2CImrPZ
	x0pxX/Dt15icS+apKBDTHlgb1k8=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=dolvbl6wZ404ia1DVm0/g2
	ufxgI=; b=uk6qyuFeIKaYf1aE4yhZbrh6YOdUfEK0Dv/HvsQ1PWlQ80oTUZnKqZ
	i6iXsTxgcM5VpAECCA298FK4qp8b7NzpI4eUYehrUSA+h3rUQRPNGgvS04z1MFDx
	U2MKQVYlW+fNaWMZiRqhH9853ZX3cVgd9WDzMCuVp4RjGBuYDwnag=
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=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=cherry
X-HELO: smtp-out-no.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Update mingw-w64 headers
To: cygwin AT cygwin DOT com
References: <CALK-3mJGJf3oXs+3OVc7E1C=t=jkiy7J_4rE95+HR9kj9sesDw AT mail DOT gmail DOT com> <eca2047c-1039-5c88-a29f-422d1448e40a AT SystematicSw DOT ab DOT ca> <CALK-3mKT=HLf2-_En+jv2twgEVq8Az+RZRTEYu0JuKf+-RPhSg AT mail DOT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <c6cbb16e-9b2c-320e-aaa8-5f69bc6ea6af@SystematicSw.ab.ca>
Date: Mon, 28 Oct 2019 23:00:19 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CALK-3mKT=HLf2-_En+jv2twgEVq8Az+RZRTEYu0JuKf+-RPhSg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-10-28 22:48, Biswapriyo Nath wrote:
> I did not mean the release page [1]. I mean the cygwin headers is older
> than the current mingw-w64 git repository [2]. The latest tag is v6.0.0.
> [3]
> 
> Wait, did you mean there should be a new "stable" tag or release in
> mingw-w64 so that cygwin can import it?
> 
> [1]: http://mingw-w64.org/doku.php/download
> [2]: https://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/
> [3]: https://sourceforge.net/p/mingw-w64/mingw-w64/ref/master/tags/

Did you read what I posted or check the content at the links?

Mingw64 release is 6.0.0 and so are Cygwin packages mingw64-*86-headers!

Mingw64 6 was released at the end of last year and Cygwin packages were updated
to 6 at the start of this year.

Where is the discrepancy between Mingw64 and Cygwin headers?

The Mingw64 master/HEAD/tip may not be identical to current Cygwin, as Cygwin
tracks stable package release sources, but will sometimes cherry pick CVE fixes
to patch between releases.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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