X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=GgkJU7CiL18AhE4rjUqaJvInML8lV3scfDQI5Zpiy5bI3UbkQOv2v
	KSa/8PHSamOm4FdZPgcpdSHWBBikYWDDR7HkQQzGt6dHHq94KF5+EZVapWiuwNHt
	2SU8EEXsbhH0W/LY01rEoqvHvdxc3mfd9SXoy3Z0Cn66P1tyVVObTQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=6vfkwybbtEoHqESjmQjhWi0ZQs0=; b=OKuvop/0byYsq2r29yodEb07DGZC
	skTue4P/A+DX3QLOLVelyiE96lBUOtOoFSJYvIyG6R9bnBwZqqP0l+a+1pg1oYDd
	h2iByu2hBHhTCKk8az9F8jqhc+VpGFRveG2iXUqb9UBwi+aOa3Q16swN2ZuZaRdo
	lQuFzXjo0YweCqQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
Date:	Wed, 30 Jan 2019 19:53:21 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2
Message-ID:	<20190130185321.GL3912@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<announce DOT 20190130140314 DOT GG3912 AT calimero DOT vinschen DOT de> <5f727fe5-1c98-3fb5-30f3-9cb1120d4aa4 AT SystematicSw DOT ab DOT ca> <20190130173104 DOT GK3912 AT calimero DOT vinschen DOT de> <0dd6e7ce-a503-e181-97a3-0d6e289251e5 AT SystematicSw DOT ab DOT ca>
MIME-Version:	1.0
In-Reply-To:	<0dd6e7ce-a503-e181-97a3-0d6e289251e5@SystematicSw.ab.ca>
User-Agent:	Mutt/1.10.1 (2018-07-13)

--eP8xGX2lG1UwfyBj
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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"

-----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--

- Raw text -