public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.9
Date: Thu, 10 Dec 2015 09:17:00 -0000	[thread overview]
Message-ID: <20151210091726.GA3507@calimero.vinschen.de> (raw)
In-Reply-To: <5668A50F.6060805@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Dec  9 23:02, Marco Atzeri wrote:
> On 08/12/2015 22:48, Corinna Vinschen wrote:
> >On Dec  8 22:03, Achim Gratz wrote:
> >>Corinna Vinschen writes:
> >>>I released TEST version 2.4.0-0.9 of Cygwin.
> >>>
> >>>- This version patches the Windows 10 1511 workaround added to
> >>>   2.4.0-0.7.  Cygwin now always uses a self-created main thread stack
> >>>   in a memory area with very low probability of collision with the OS.
> >>>   The fix addresses the problem reported in
> >>>   https://cygwin.com/ml/cygwin/2015-12/msg00077.html
> >>
> >>Interestingly enough this also seems to have solved a stubborn fork
> >>problem on Windows 8.1 when trying to start emacs-x11 over SSH from my
> >>Linux box.
> >
> >Huh, interesting.
> >
> >
> >Corinna
> >
> 
> also pure-ftpd fork issue on W7-64 bit seems solved...

It gets better :}


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-10  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 15:57 Corinna Vinschen
2015-12-08 21:03 ` Achim Gratz
2015-12-08 21:48   ` Corinna Vinschen
2015-12-09 22:03     ` Marco Atzeri
2015-12-10  9:17       ` Corinna Vinschen [this message]
2015-12-10  2:08 ` kuaf
2015-12-10  6:09   ` 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=20151210091726.GA3507@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).