From: Dave Taht <dave.taht@gmail.com>
To: Kathleen Nichols <nichols@pollere.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Schedule for publication of "Controlling Queue Delay"
Date: Wed, 2 May 2012 10:49:41 -0700 [thread overview]
Message-ID: <CAA93jw53FoevqNp7t1f48H6upsJ3dDkGbeXd20W0c7VVSFCx8Q@mail.gmail.com> (raw)
In-Reply-To: <4FA17034.5010000@pollere.com>
On Wed, May 2, 2012 at 10:34 AM, Kathleen Nichols <nichols@pollere.com> wrote:
>
> Well, whatever. I just want to get an implementation and get it right. In
> this field, we have folks from all over the world and there are a lot of
> things we don't pronounce the same (those aussies need to learn to
> speak some language the rest of us can understand!) For what it's
> worth, my thinking is:
>
> Co is from "controlled", "caw"
> and Del is from "delay", "del"
>
The CamelCase leads naturally to a pronounciation of Coh Del
coddle rhymes with bridle in most dialects I can think of, esr (not on
this list presently) would know... it's the 'o' that will be
repronounced, regardless,
and spelling it with the 'a' sound doesn't help in maine.
That said, I do like vowels, so codel (non-camelcase) would be good,
and it is a valid word already, so existing usages *might not* cause
problems, but do a google search for it's existing googlejuice, and
decide.
codl is short and relatively unambiguous. not a lot of googlejuice
either. I like it.
> On 5/2/12 10:23 AM, Rick Jones wrote:
>>
>>> P.S. Let's try to be pro-active about pronunciation: I like the way
>>> Kathie said "coddle", rather than Co-Del; it's sort of warm and fuzzy:
>>> the wiktionary definition is "To treat gently or with great care.",
>>> which I also like....
>>
>> Well, there is also the connotation of being overly protected :)
>>
>> If it is spelled CoDel getting it pronounced like coddle will be very
>> difficult. To get it widely pronounced like coddle it really should be
>> presented as CoDl or somesuch.
>>
>> rick
>> _______________________________________________
>> Codel mailing list
>> Codel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/codel
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next prev parent reply other threads:[~2012-05-02 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 15:11 Jim Gettys
2012-05-02 17:23 ` Rick Jones
2012-05-02 17:31 ` Jim Gettys
2012-05-02 17:34 ` Kathleen Nichols
2012-05-02 17:49 ` Dave Taht [this message]
2012-05-02 18:09 ` Rick Jones
2012-05-02 18:15 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw53FoevqNp7t1f48H6upsJ3dDkGbeXd20W0c7VVSFCx8Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=nichols@pollere.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