From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Network Neutrality is back! Let´s make the technical aspects
heard this time!'" <nnagain@lists.bufferbloat.net>,
'bloat' <bloat@lists.bufferbloat.net>
Cc: "'Dave Taht'" <dave.taht@gmail.com>,
"'Simon Kelley'" <simon@thekelleys.org.uk>,
"'Alexis Schrubbe'" <schrubbe@uchicago.edu>,
"'Benjamin Boyter'" <bboyte01@gmail.com>,
"'Nick Feamster'" <feamster@uchicago.edu>
Subject: Re: [NNagain] correctly calculating code complexity and cost
Date: Fri, 17 Nov 2023 08:06:40 -0800 [thread overview]
Message-ID: <6395D4E936B743EBB2174893DF9E54C6@SRA6> (raw)
In-Reply-To: <CAA93jw4eHMh0pQ+7VYRFWCPS9b9X0MxPyPmE2H6E+ndbvg9Txg@mail.gmail.com>
Atkinson's story, fable, folklore, or not, is AWESOME in soooo many
respects!!!!!!
[RR] ...
https://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.txt
prev parent reply other threads:[~2023-11-17 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:08 Dave Taht
2023-11-17 16:06 ` Dick Roy [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
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6395D4E936B743EBB2174893DF9E54C6@SRA6 \
--to=dickroy@alum.mit.edu \
--cc=bboyte01@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=feamster@uchicago.edu \
--cc=nnagain@lists.bufferbloat.net \
--cc=schrubbe@uchicago.edu \
--cc=simon@thekelleys.org.uk \
/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