On Feb 17 10:48, Brian Inglis wrote:
> On 2019-01-30 13:29, Corinna Vinschen wrote:
> > 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.
>
> I have zero problems with your previous considerations a
On 2019-01-30 13:29, Corinna Vinschen wrote:
> 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, Corin
On 2019-01-30 11:56, Andrey Repin wrote:
>> 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
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 n
Greetings, Brian Inglis!
> 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 diffe
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 chan
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
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 include
On Wed, Jan 30, 2019 at 11:31 AM Corinna Vinschen
wrote:
>
> On Jan 30 09:11, Brian Inglis wrote:
> >
> > 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 sho
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
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 fo
11 matches
Mail list logo
