From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2
Date: Wed, 30 Jan 2019 19:01:00 -0000 [thread overview]
Message-ID: <20190130190150.GM3912@calimero.vinschen.de> (raw)
In-Reply-To: <20190130185321.GL3912@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2884 bytes --]
On Jan 30 19:53, Corinna Vinschen wrote:
> On Jan 30 11:47, Brian Inglis wrote:
> > On 2019-01-30 10:31, Corinna Vinschen wrote:
> > > On Jan 30 09:11, Brian Inglis wrote:
> > >> On 2019-01-30 07:03, Corinna Vinschen wrote:
> > >>> I uploaded a new Cygwin test release 3.0.0-0.2
> > >>> It also changes the output of uname(2) for newly built applications.
> > >>> Applications built so far (that includes uname(1) from coreutils)
> > >>> will still print the old uname output. The new format allows for longer
> > >>> strings. Compare:
> > >>> Upcoming new uname content:
> > >>> sysname: CYGWIN_NT-10.0-17763 or CYGWIN_NT-10.0-17763-WOW64
> > >>> release: 3.0.0-335.x86_64 or 3.0.0-335.x86_64.snap
> > >>> version: 2019-01-29 19:23 UTC Build time in UTC
> > >> Re: "(*) It would really be nice not having to ask for these infos every time."
> > >> may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/UBR to
> > >> uname -s sysname to show the patch levels of installed builds, as there appears
> > >> to be substantial differences between editions and service models.
> > > Thanks for the info, but what to do with this? Is there a thorough
> > > description somewhere to allow deciphering what this means to us?
> >
> > UBR Update Build Revision appears to be incremented for each patch set released
> > for the W10 feature set OS build, to complete a unique revision id, similar to
> > Cygwin 335 above.
> > Would save those of us who know to, having to also run and append the output of
> >
> > $ cmd /c ver
> >
> > Microsoft Windows [Version 10.0.17134.523]
> >
> > and save asking those who don't know that, in case the revision makes a difference.
> > Insider build feature sets bump the builds, and patch sets bump those revisions;
> > up to base releases with known feature sets, builds, and revisions; then patch
> > Tuesdays bump those revisions higher; so you can tell if installs are Insider,
> > base, or patched.
>
> I'm not so sure this makes sense from a Cygwin perspective. We're
> interested in the major releases introducing changing and/or new
> functionality. The monthly updates don't do that so they have no
> meaning to us.
>
> I just wonder if we should replace the build number with the ReleaseId
> (i.e. 17763 vs. 1809), but that excludes the fast lane updates from
> being visible.
On second thought there's also the format discrepancy. Right now the
new uname crates the version string like "10.0-17763", but it might be
better to use "10.0.17763", replacing the dash with a dot, to follow
more closely the OS layout. On third thought it seems prudent to
print either
10.0-1809{-WOW64}
or
10.0.17763.253{-WOW64}
Hmm. The second form appears to make the most sense, actually.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-30 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:06 Corinna Vinschen
2019-01-30 16:11 ` Brian Inglis
2019-01-30 17:31 ` Corinna Vinschen
2019-01-30 18:28 ` Richard Campbell
2019-01-30 18:47 ` Brian Inglis
2019-01-30 18:53 ` Corinna Vinschen
2019-01-30 19:01 ` Corinna Vinschen [this message]
2019-01-30 20:29 ` Corinna Vinschen
2019-02-17 18:20 ` Brian Inglis
2019-02-18 8:45 ` Corinna Vinschen
2019-01-30 19:05 ` Andrey Repin
2019-01-31 18:15 ` Brian Inglis
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=20190130190150.GM3912@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).