From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST)
Date: Thu, 26 Sep 2019 14:38:00 -0000 [thread overview]
Message-ID: <ef3df534-d988-1fba-034c-d66583427573@cornell.edu> (raw)
In-Reply-To: <20190926195636.5c7c146d79ebb2b38ac9cb22@nifty.ne.jp>
On 9/26/2019 6:56 AM, Takashi Yano wrote:
> On Wed, 25 Sep 2019 21:09:16 +0900
> Takashi Yano wrote:
>> On Tue, 24 Sep 2019 17:37:40 +0000
>> Ken Brown wrote:
>>> I just noticed a glitch that goes back to the first commit of the new PTY code
>>> (commit 169d65a5774acc76ce3f3feeedcbae7405aa9b57):
>>>
>>> If I run 'setup_x86 -h' in mintty, there's no output. Prior to that commit, the
>>> help output is printed, as expected.
>>
>> I will look into this problem. Please wait a while.
>
> I have fixed this problem and submitted a patch just now.
Confirmed.
Thanks.
Ken
--
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:[~2019-09-26 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 16:24 Ken Brown
2019-09-24 7:38 ` Michael Haubenwallner
2019-09-24 12:50 ` Ken Brown
2019-09-24 23:05 ` Ken Brown
2019-09-25 18:30 ` Takashi Yano
2019-09-26 12:51 ` Takashi Yano
2019-09-26 14:38 ` Ken Brown [this message]
2019-10-02 14:04 ` Michael Haubenwallner
2019-10-02 18:24 ` Ken Brown
2019-10-03 10:44 ` Takashi Yano
2019-10-10 10:44 ` Michael Haubenwallner
2019-10-11 9:25 ` Takashi Yano
2019-10-14 11:07 ` Michael Haubenwallner
2019-10-16 12:32 ` Takashi Yano
2019-10-18 11:36 ` Takashi Yano
2019-10-16 14:34 ` Takashi Yano
2019-10-16 16:34 ` Michael Haubenwallner
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=ef3df534-d988-1fba-034c-d66583427573@cornell.edu \
--to=kbrown@cornell.edu \
--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).