From: Thomas Wolff <towo@towo.net>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
cygwin-developers@cygwin.com, Ken Brown <kbrown@cornell.edu>,
Yaakov Selkowitz <yselkowi@redhat.com>,
Jon TURNEY <jon.turney@dronecode.org.uk>
Subject: Re: [PATCH v8 1/1] Cygwin: pty: add pseudo console support.
Date: Tue, 27 Aug 2019 08:39:00 -0000 [thread overview]
Message-ID: <0e5a34ce-3b92-f224-addf-89239fc6a84a@towo.net> (raw)
In-Reply-To: <20190827082427.GT11632@calimero.vinschen.de>
Am 27.08.2019 um 10:24 schrieb Corinna Vinschen:
> On Aug 22 00:42, Takashi Yano wrote:
>> - Support pseudo console in PTY. Pseudo console is a new feature
>> in Windows 10 1809, which provides console APIs on virtual
>> terminal. With this patch, native console applications can work
>> in PTY such as mintty, ssh, gnu screen or tmux.
> Great, the stderr problem is definitely fixed. I've extremely limited
> time until late October, so I'll push the release into late October or
> November. I think, given the time frame, we could easily push this
> change into 3.1.
>
> Does anybody have problems with that?
I don't, but as it's a big issue, it may be reasonable to have it in a
test release well before final release.
Thomas
next prev parent reply other threads:[~2019-08-27 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 15:43 [PATCH v8 0/1] Pseudo console support in PTY (v8) Takashi Yano
2019-08-21 15:43 ` [PATCH v8 1/1] Cygwin: pty: add pseudo console support Takashi Yano
2019-08-27 8:24 ` Corinna Vinschen
2019-08-27 8:39 ` Thomas Wolff [this message]
2019-08-27 8:47 ` Corinna Vinschen
2019-08-27 15:52 ` Takashi Yano
2019-08-27 15:58 ` Corinna Vinschen
2019-08-23 22:30 ` [PATCH v8 0/1] Pseudo console support in PTY (v8) Thomas Wolff
2019-08-24 6:18 ` Takashi Yano
2019-08-24 22:22 ` Thomas Wolff
2019-08-27 18:06 ` Takashi Yano
2019-08-29 6:49 ` Thomas Wolff
2019-08-29 8:05 ` Corinna Vinschen
2019-08-29 11:58 ` Corinna Vinschen
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=0e5a34ce-3b92-f224-addf-89239fc6a84a@towo.net \
--to=towo@towo.net \
--cc=cygwin-developers@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
--cc=kbrown@cornell.edu \
--cc=takashi.yano@nifty.ne.jp \
--cc=yselkowi@redhat.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).