From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Tue, 28 Jan 2020 20:21:00 -0000 [thread overview]
Message-ID: <87imkvgwnu.fsf@Rainer.invalid> (raw)
In-Reply-To: <6143b338-38ca-6157-711d-fae6ef431297@gmail.com> (Marco Atzeri's message of "Tue, 28 Jan 2020 21:04:10 +0100")
Marco Atzeri writes:
> I just found that my W10 Home is 1909 build 18363.592 so probably was
> updated as your around mid Jan
>
> https://docs.microsoft.com/en-us/windows/release-information/
>
> But Corporate versions have different time table and patch
Enterprise is, yes.
> the one I have is Version 1709 Build 16299.15
> It seems Corporate IT is forgetting to update it at all.
They currently have at least three different release branches which are
supported (for the clients, server versions is yet another story). At
my company they switched us to 1803 recently. Going forward I think
there will be fewer supported options even for Enterprise if I read
things correctly. But MS will have to wait out until the current
support periods end.
> This release had caused problems to some AV, so may be is changing
> the play in area that are causing problems also to us.
I still think it's a latent bug that manifests just now.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-28 20:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 16:55 Marco Atzeri
2020-01-25 18:15 ` Brian Inglis
2020-01-27 6:54 ` Marco Atzeri
2020-01-25 20:36 ` Achim Gratz
2020-01-26 6:58 ` Marco Atzeri
2020-01-26 8:05 ` ASSI
2020-01-26 8:38 ` Marco Atzeri
2020-01-27 6:45 ` Marco Atzeri
2020-01-27 11:33 ` Takashi Yano
2020-01-28 6:41 ` Marco Atzeri
2020-01-28 14:55 ` Takashi Yano
2020-01-29 9:44 ` Corinna Vinschen
2020-01-29 12:19 ` Marco Atzeri
2020-01-29 13:46 ` Takashi Yano
2020-01-29 15:11 ` Takashi Yano
2020-01-29 15:32 ` Corinna Vinschen
2020-01-29 15:34 ` Corinna Vinschen
2020-01-29 16:08 ` Takashi Yano
2020-01-29 17:57 ` Corinna Vinschen
2020-01-30 21:05 ` Brian Inglis
2020-01-30 21:34 ` Marco Atzeri
2020-01-28 17:26 ` ASSI
2020-01-28 20:04 ` Marco Atzeri
2020-01-28 20:21 ` Achim Gratz [this message]
2020-01-26 2:42 ` Takashi Yano
2020-01-26 5:11 ` Takashi Yano
2020-01-26 10:24 ` Marco Atzeri
2020-01-26 10:31 ` Takashi Yano
2020-01-29 0:03 ` Hans-Bernhard Bröker
2020-01-29 0:39 ` Hans-Bernhard Bröker
2020-01-29 5:10 ` Marco Atzeri
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=87imkvgwnu.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).