From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: Rare character glitch in pty?
Date: Mon, 7 Aug 2023 20:38:12 +0900 [thread overview]
Message-ID: <20230807203812.32ab673c1b452b1e0f148486@nifty.ne.jp> (raw)
In-Reply-To: <ZNCrIG9bMSRpO64m@calimero.vinschen.de>
On Mon, 7 Aug 2023 10:28:16 +0200
Corinna Vinschen wrote:
> On Aug 5 17:10, Takashi Yano wrote:
> > On Sat, 5 Aug 2023 09:53:30 +0200
> > Thomas Wolff wrote:
> > > Great! Thank you for fixing such a subtle issue in a core component.
> > > Any chance to get this back-ported to 3.4.7 (as the last version to
> > > support ... whatever)?
> >
> > I hope 3.4.8 would be released before 3.5.0. Cygwin 3.4.7 has
> > another big issue:
> > https://sourceware.org/pipermail/newlib/2023/020443.html
> > so, I am not happy if 3.4.7 is the final cygwin-3_4-branch
> > release.
>
> We certainly do a 3.4.8 and probably more 3.4 versions before 3.5.
I was relieved to hear that. Thanks!
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2023-08-07 11:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f0bfdf8-a557-0540-0367-6846406f941d@towo.net>
2023-08-01 21:05 ` Thomas Wolff
2023-08-01 21:27 ` Corinna Vinschen
2023-08-02 6:36 ` cygwin build Thomas Wolff
2023-08-02 6:42 ` Takashi Yano
2023-08-02 8:09 ` Corinna Vinschen
2023-08-03 8:21 ` Thomas Wolff
2023-08-03 13:12 ` Jon Turney
2023-08-05 18:18 ` Thomas Wolff
2023-08-05 22:20 ` Takashi Yano
2023-08-06 6:51 ` Thomas Wolff
2023-08-06 18:53 ` Jon Turney
2023-08-07 6:11 ` Thomas Wolff
2023-08-07 8:25 ` Corinna Vinschen
2023-08-03 13:13 ` Jon Turney
2023-08-01 22:35 ` Rare character glitch in pty? Takashi Yano
2023-08-02 6:32 ` Thomas Wolff
2023-08-02 8:00 ` Takashi Yano
2023-08-02 13:16 ` Takashi Yano
2023-08-04 8:52 ` Takashi Yano
2023-08-04 11:33 ` Takashi Yano
2023-08-05 7:53 ` Thomas Wolff
2023-08-05 8:10 ` Takashi Yano
2023-08-07 8:28 ` Corinna Vinschen
2023-08-07 11:38 ` Takashi Yano [this message]
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=20230807203812.32ab673c1b452b1e0f148486@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-developers@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).