From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current master.
Date: Mon, 28 Aug 2023 23:20:27 +0900 [thread overview]
Message-ID: <20230828232027.0b934a4df82a831c454d5419@nifty.ne.jp> (raw)
In-Reply-To: <DM8PR09MB7095A19F19A16FDCABAD03F6A5E0A@DM8PR09MB7095.namprd09.prod.outlook.com>
On Mon, 28 Aug 2023 14:07:44 +0000
"Lavrentiev, Anton (NIH/NLM/NCBI) [C]" wrote:
> > For message-oriented sockets, a zero-length transport datagram is sent.
>
> And how is that acceptable? This will interject a message into some application protocol,
> which may not be expected at the application level.
Yeah, due to these undesired behaviours, we decided not to adopt
this patch. Instead, we reverted the original patch.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2023-08-28 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 21:05 Takashi Yano
2023-08-24 3:31 ` Takashi Yano
2023-08-24 8:59 ` Corinna Vinschen
2023-08-25 8:48 ` Takashi Yano
2023-08-25 10:50 ` Corinna Vinschen
2023-08-25 12:08 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-25 12:23 ` Corinna Vinschen
2023-08-25 13:19 ` Corinna Vinschen
2023-08-25 23:27 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 13:52 ` Corinna Vinschen
2023-08-26 14:15 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 14:34 ` Corinna Vinschen
2023-08-25 19:29 ` Takashi Yano
2023-08-26 14:08 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-26 23:41 ` Takashi Yano
2023-08-28 13:37 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-28 13:46 ` Takashi Yano
2023-08-28 14:07 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-08-28 14:20 ` 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=20230828232027.0b934a4df82a831c454d5419@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).