From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: RE: Re: Updated: coreutils 8.32
Date: Sun, 22 May 2022 17:31:22 +0000 [thread overview]
Message-ID: <VI1P18901MB0062E9A31A35035C81C7CE22A4D59@VI1P18901MB0062.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB6P18901MB00557557275D578C5D4921A9A4D59@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
>> 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
Thank you.
> What products or processes does it affect negatively, and are there
> arguments for suppression, other than backward compatibility?
None central. I have a script with sequenced
case `uname -s` in
allowing for multiple platforms and it wobbled with this change.
I will rewrite it.
Thanks for clarity.
Fergus
prev parent reply other threads:[~2022-05-22 17:31 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
2022-05-22 16:38 ` Brian Inglis
2022-05-22 17:31 ` Fergus Daly [this message]
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=VI1P18901MB0062E9A31A35035C81C7CE22A4D59@VI1P18901MB0062.EURP189.PROD.OUTLOOK.COM \
--to=fergusd84@outlook.com \
--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).