public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: w32api-{headers,runtime}-7.0.0-1 (x86/x86_64)
Date: Thu, 14 Nov 2019 15:36:00 -0000	[thread overview]
Message-ID: <5f2579f2-a99f-0bba-5070-c49c57ff8802@SystematicSw.ab.ca> (raw)
In-Reply-To: <CALK-3m+pjL5m6oprwRyU90Cp=iX3LX1WDdAd+96SQh=kszfSNA@mail.gmail.com>

On 2019-11-14 01:55, Biswapriyo Nath wrote:
> Also, w32api-headers version 7 for x86_64 is missing.
> Link: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=w32api&arch=x86_64

Calm problems now resolved:
Search Results
Found 6 matches for w32api-headers
cygwin32-w32api-headers-3.2.0-1 - Win32 API headers for Cygwin 32bit toolchain
cygwin32-w32api-headers-4.0.4-1 - Win32 API headers for Cygwin 32bit toolchain
w32api-headers-5.0.2-1 - MinGW-w64 Windows API headers for Cygwin
w32api-headers-5.0.3-1 - MinGW-w64 Windows API headers for Cygwin
w32api-headers-5.0.4-1 - MinGW-w64 Windows API headers for Cygwin
w32api-headers-7.0.0-1 - MinGW-w64 Windows API headers for Cygwin

Shouldn't cygwin{32,64}-win32api-{headers,runtime}-7.0.0-1 (x86/x86_64) also be
available/updated at the same time?

-- 
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

  reply	other threads:[~2019-11-14 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 16:37 JonY
2019-11-14  4:58 ` JonY
2019-11-14 15:14   ` [ANNOUNCEMENT] " Biswapriyo Nath
2019-11-14 15:36     ` Brian Inglis [this message]
2019-11-14 23:53       ` JonY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f2579f2-a99f-0bba-5070-c49c57ff8802@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).