public inbox for [email protected]
 help / color / mirror / Atom feed
From: Reece <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: io_uring is a regression over 16 year old aio/io_submit, 2+ decades of Microsoft NT, and *BSD circa 1997-2001
Date: Thu, 4 May 2023 20:37:38 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Does this mean you stopped after the part where I cited 3 APIs including 
an old Linux interface (16+ years old), FreeBSD's implementation, and a 
Windows NT interface that all predate a hypothetical 14 year old? I 
guess this means modern Linux is less mature than both its' former -16 
year old self and a hypothetical 14 year old.

On 04/05/2023 20:31, Jens Axboe wrote:
> Maybe less anonymous then, but the tone is still way out of line and
> not acceptable. If you don't want to be perceived as an angry 14 year
> old, I suggest you rewrite your email and try again. I stopped half way
> through that steaming pile of words.
>
>
> On 5/4/23 1:29 PM, Reece wrote:
>> what are you talking about? i literally cc'd you alongside the mailing list. how is an email alongside commits tied to my real legal name "anonymous" trolling?
>>
>> On 04/05/2023 20:27, Jens Axboe wrote:
>>> On 5/4/23 1:20?PM, Reece wrote a pile of garbage.
>>>
>>> If you have constructive criticism, the list is open to discuss it.
>>> Sending trolly garbage anonymously is, however, neither welcome nor a
>>> productive approach.
>>>

      parent reply	other threads:[~2023-05-04 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 19:20 io_uring is a regression over 16 year old aio/io_submit, 2+ decades of Microsoft NT, and *BSD circa 1997-2001 Reece
2023-05-04 19:27 ` Jens Axboe
     [not found]   ` <[email protected]>
     [not found]     ` <[email protected]>
2023-05-04 19:37       ` Reece [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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