On 2020-08-25 05:04, Corinna Vinschen wrote:
> Hi Brian,
>
> On Aug 24 14:10, Brian Inglis wrote:
>> winsup/doc/faq-api.xml,faq-programming.xml: change Win32 to Windows
>
> Didn't we agree on WinAPI? Windows is fine when used in the context of
> the OS, but Win32 was mainly used to denote the
based on material from t...@iana.org mailing list sources
---
winsup/doc/faq-api.xml | 29 +
1 file changed, 25 insertions(+), 4 deletions(-)
diff --git a/winsup/doc/faq-api.xml b/winsup/doc/faq-api.xml
index 829e4d7febd8..365e301555a5 100644
---
FAQ updates from suggestions made in various posts
Brian Inglis (3):
winsup/doc/faq-setup.xml,faq-using.xml: update setup FAQ
winsup/doc/faq-api.xml,-programming.xml: change Win32 to Windows or Windows
API
winsup/doc/faq-api.xml(faq.api.timezone): explain time zone updates
---
winsup/doc/faq-api.xml | 10 +-
winsup/doc/faq-programming.xml | 20 ++--
2 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/winsup/doc/faq-api.xml b/winsup/doc/faq-api.xml
index 313f15d37c4d..829e4d7febd8 100644
--- a/winsup/doc/faq-api.xml
+++
change all kinds of setup references to "the Cygwin Setup program";
emphasize 64 bit and deemphasize 32 bit;
update options list;
explain why installing everything is now extremely inadvisable, with stats
---
winsup/doc/faq-setup.xml | 229 ++-
Hi Brian,
On Aug 24 14:10, Brian Inglis wrote:
> winsup/doc/faq-api.xml,faq-programming.xml: change Win32 to Windows
Didn't we agree on WinAPI? Windows is fine when used in the context of
the OS, but Win32 was mainly used to denote the API. So "Windows API"
or, better, WinAPI, should be used
Hi Mark,
On Aug 25 00:29, Mark Geisert wrote:
> Hi Corinna,
> Well, this patch turned out to be half-baked. Locking is working correctly
> because USE_LOCKS was set to 1 for malloc.cc's compilation. The torture
> test I run validated that. OTOH as you said, MSPACES was set 1 for
> malloc.cc
Hi Corinna,
Well, this patch turned out to be half-baked. Locking is working correctly
because USE_LOCKS was set to 1 for malloc.cc's compilation. The torture test I
run validated that. OTOH as you said, MSPACES was set 1 for malloc.cc but 0 for
malloc_wrapper.cc. So this patch yields a
