public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: TCP_CORK (aka TCP_NOPUSH) does not work
Date: Wed, 31 Jul 2019 22:11:00 -0000	[thread overview]
Message-ID: <ef47522d-a1f1-b9a8-5e91-52306b49e38c@cornell.edu> (raw)
In-Reply-To: <BL0PR0901MB4308676B47ABA190207BD075A5DF0@BL0PR0901MB4308.namprd09.prod.outlook.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 614 bytes --]

On 7/31/2019 5:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>> Linux and BSD options are not available, whatever the .h #defines.
> 
> Unsupported options should not be shown as features in the headers.

Why not just write a patch to fix this and send it to the cygwin-patches 
mailing list?  It would take much less time than continuing this discussion.

Ken
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2019-07-31 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 21:00 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-31 22:11 ` Ken Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-31 23:16 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-31  4:49 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-31 19:32 ` Brian Inglis
2019-07-30 21:30 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-31  3:50 ` Brian Inglis

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=ef47522d-a1f1-b9a8-5e91-52306b49e38c@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).