From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31141 invoked by alias); 30 Jan 2019 20:29:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31134 invoked by uid 89); 30 Jan 2019 20:29:52 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-100.4 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=uploaded X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.134) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 30 Jan 2019 20:29:50 +0000 Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1M4roN-1gplyF0z8Z-0023QL for ; Wed, 30 Jan 2019 21:29:48 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id A9E2CA825EB; Wed, 30 Jan 2019 21:29:47 +0100 (CET) Date: Wed, 30 Jan 2019 20:29:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2 Message-ID: <20190130202947.GO3912@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5f727fe5-1c98-3fb5-30f3-9cb1120d4aa4@SystematicSw.ab.ca> <20190130173104.GK3912@calimero.vinschen.de> <0dd6e7ce-a503-e181-97a3-0d6e289251e5@SystematicSw.ab.ca> <20190130185321.GL3912@calimero.vinschen.de> <20190130190150.GM3912@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TMTfqzsZeEKgETVO" Content-Disposition: inline In-Reply-To: <20190130190150.GM3912@calimero.vinschen.de> User-Agent: Mutt/1.10.1 (2018-07-13) X-SW-Source: 2019-01/txt/msg00301.txt.bz2 --TMTfqzsZeEKgETVO Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2836 On Jan 30 20:01, Corinna Vinschen wrote: > 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 applicatio= ns. > > > >>> 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. > > > [...] > > > $ cmd /c ver > > >=20 > > > Microsoft Windows [Version 10.0.17134.523] > > >=20 > > > 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. > >=20 > > 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. > >=20 > > 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. >=20 > 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 >=20 > 10.0-1809{-WOW64} >=20 > or >=20 > 10.0.17763.253{-WOW64} >=20 >=20 > Hmm. The second form appears to make the most sense, actually. But then again, no OS before W10 printed that info, e.g.: Microsoft Windows [Version 6.3.9600] We also have to make sure we're not breaking scripts, especially autoconf etc., so on forth thought, I'll rather stick to the current format. Corinna --=20 Corinna Vinschen Cygwin Maintainer --TMTfqzsZeEKgETVO Content-Type: application/pgp-signature; name="signature.asc" Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxSCTsACgkQ9TYGna5E T6CXNxAAh4zijYHvzHG9k15D+dXQZygWyzcMAodASVrbOD3FjWQ6Hb5nYaA6WYsP jdwds6kS2Awt8NTsEQFTjdQ+cU01koN7winnYP3Smsr6qReb6Qv8nz7sfxGMj6MB qC1emCDmGswNKRv6boQ2Td96h+ZMuOcks0eHTbDN9G/ZLYnZmJgUczHSXz0Mfrap cytzD+yte+n1osxNTkUZ+slxx3/FFxZULThaNBXaBVNA+Vt60t4xvBUWew7UOMme YKHbcE3X2FdBDhldxUujmVw6XeuDspPV242wNnqJb1XNJVS8D3xycxBGPaQ4ELFA adhXlx30xzjs/fOvCw8llgOdgjM6ScYhZ/YvyT60TZ2XuC6JKOPkK/xzoNzkdTgA bE5mpju2aSumQlbhcSHO4NJWn+03b1dnSp5i4ghzWvsshP47H928wP5G1ueM08i7 7JLgeC90uUZ5UQeklmnBPo8OhXB/GSuD0Kw/mxsQptZHMflvJqMk0wCYfJkDm4F6 bQY2Y7cP+TpQiZaDdwmT4NhZ+weGg3VosaYpZdSKdTNwoETpz2k2r7KXOOuEzCR7 nEhL/hHypdOnk1bmFjBSITTrcQy0EtkNfH7WdjuVHarggrhi5mFR5zDWPnSfK/VH v2CRIJlHrmuQL8eMVGDCbKMZGaeFpIsXwR1yRrF4RT70QvD1Z/8= =MnNn -----END PGP SIGNATURE----- --TMTfqzsZeEKgETVO--