From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Updated: coreutils 8.32
Date: Sun, 22 May 2022 09:24:53 -0600 [thread overview]
Message-ID: <628ba81b-a07b-9ee1-05cb-2dcdadc43d3d@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB6P18901MB00557557275D578C5D4921A9A4D59@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
On 2022-05-21 23:54, Fergus Daly wrote:
> I've just updated coreutils. I don't use test versions. So I have
> $ uname --version
> uname (GNU coreutils) 8.32
> Packaged by Cygwin (8.32-1)
> Now on 32-bit Cygwin I get
> $ uname -s
> CYGWIN_NT-10.0-19044-WOW64 [ previously CYGWIN_NT-10.0-WOW ]
> And on 64-bit Cygwin I get
> $ uname -s
> CYGWIN_NT-10.0-19044 [ previously CYGWIN_NT-10.0 ]
> Packaging error?
That build is a value we have said for years we would make visible for
easier determination of Windows version used (21H2 for you and I),
previously only visible in /proc/version:
$ head /proc/version
CYGWIN_NT-10.0-19044 version 3.3.5-341.x86_64 (corinna@calimero) (gcc
version 11.2.0 20210728 (Fedora Cygwin 11.2.0-2) (GCC) ) 2022-05-13
12:27 UTC
What products or processes does it affect negatively, and are there
arguments for suppression, other than backward compatibility?
--
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.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-05-22 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 5:54 Fergus Daly
2022-05-22 15:24 ` Brian Inglis [this message]
2022-05-22 16:38 ` Brian Inglis
2022-05-22 17:31 ` Fergus Daly
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=628ba81b-a07b-9ee1-05cb-2dcdadc43d3d@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).