From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38274 invoked by alias); 30 Jan 2019 18:53:26 -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 38266 invoked by uid 89); 30 Jan 2019 18:53:26 -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=insider, 10.0.17134.523, installs, patched X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.74) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 30 Jan 2019 18:53:25 +0000 Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MnagF-1hXZax2H5x-00jZfo for ; Wed, 30 Jan 2019 19:53:22 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id 049F1A825EB; Wed, 30 Jan 2019 19:53:22 +0100 (CET) Date: Wed, 30 Jan 2019 18:53:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2 Message-ID: <20190130185321.GL3912@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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eP8xGX2lG1UwfyBj" Content-Disposition: inline In-Reply-To: <0dd6e7ce-a503-e181-97a3-0d6e289251e5@SystematicSw.ab.ca> User-Agent: Mutt/1.10.1 (2018-07-13) X-SW-Source: 2019-01/txt/msg00295.txt.bz2 --eP8xGX2lG1UwfyBj Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2314 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 lon= ger > >>> 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 eve= ry time." > >> may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/U= BR to > >> uname -s sysname to show the patch levels of installed builds, as ther= e 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? >=20 > UBR Update Build Revision appears to be incremented for each patch set re= leased > for the W10 feature set OS build, to complete a unique revision id, simil= ar to > Cygwin 335 above. > Would save those of us who know to, having to also run and append the out= put of >=20 > $ 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 d= ifference. > Insider build feature sets bump the builds, and patch sets bump those rev= isions; > 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 Ins= ider, > 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. Corinna --=20 Corinna Vinschen Cygwin Maintainer --eP8xGX2lG1UwfyBj Content-Type: application/pgp-signature; name="signature.asc" Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxR8qEACgkQ9TYGna5E T6DVfw//SSShVqio5S+tK5cQPbvaM8Kdh67L6yjqCrRUKuSAj6fsgYn7dAlU9gnN LOJmuFOTkKeGr9bUeCksQVf4QP+W7CKxhzm0S/6UnBCXj4U2o+4R4ZMJEWtktk20 y9RySJJ737t1dU2aAc+ue0zvFOecIWOHpVmEoWWfyGL3SEXxrQJocBsBwaspamFm oT0tdtVni28xSD/vOwn7/uLy+NjoGCyaAI4vsVR24BBYtd5iJrVh6Fg6VNrw86i0 uKwF3qIbuAZu+h/XiSyhRoMaiKYsEVE53cgmtx2bP+grDdoESbHiitEM3soII6FK Xf+Z7RyRxZJD9gJ22g1l+Fgm3sutiYfQDfQoVkxnOyyfpr8InFyi2dedAvmNpJwv jsO4iwURd2/iazYhckR95Me+xKQLNyATjWT7pk7v3BpSiveerHnajkTlcTfJ+C22 LYPltrwsu6ux3IkHyKwpqTMyw+8FR4mcChRVS12lH3BcMGkcv7C+ZHoHXE/0LqaH 7m8wotzHVtSXnOeniconc4wax5E006AqjjHZFfuwuQAXaKxRZJidiRcnQfwSxTMu mEqqZpS7/fZLUaTJfk6KelGbrrNAwyPGCtnyTa6suH3LRGAeKkmAj7XotGGm4Z2n TVro6wDvSUema2hlYL4T1Kl4XsmEyiMoO6e+XWMi18fMJTx5nV0= =hBur -----END PGP SIGNATURE----- --eP8xGX2lG1UwfyBj--