From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Mark Chambers <markc@mail.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: "I2C" versus "IIC"
Date: Wed, 13 Oct 2004 14:56:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0410131453130.13195@localhost.localdomain> (raw)
In-Reply-To: <005601c4b155$8ae3fbf0$0301a8c0@chuck2>
On Wed, 13 Oct 2004, Mark Chambers wrote:
> ----- Original Message -----
> From: "Robert P. J. Day" <rpjday@mindspring.com>
> To: "Embedded PPC Linux list" <linuxppc-embedded@ozlabs.org>
> Sent: Wednesday, October 13, 2004 2:26 PM
> Subject: "I2C" versus "IIC"
>
> My vote, since nobody asked, would be "I2C". I've always heard people
> say "I squared C", and since only CBS can get superscripts out of ASCII
> I2C is about as close as you can get. I2C is more unique and hence
> a more readily recognizable acronym.
>
> But I'm sure we could get about 50/50 voting on this.
oh, probably. :-) i realize it sounds nitpicky and pedantic, but it
would have been nice if the source was consistent on this. but based
on my grep of the tree, i don't see that that's possible -- too many
examples of each. it's kind of a mess. personally, i'd prefer a
consistent usage of "i2c" or "I2C" as well, but i just don't see it
happening.
rday
next prev parent reply other threads:[~2004-10-13 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 18:26 "I2C" versus "IIC" Robert P. J. Day
2004-10-13 18:50 ` Mark Chambers
2004-10-13 18:56 ` Robert P. J. Day [this message]
2004-10-13 19:10 ` annamaya
2004-10-13 19:34 ` Eugene Surovegin
2004-10-13 19:40 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 20:18 VanBaren, Gerald (AGRE)
2004-10-13 20:26 ` Matt Porter
2004-10-13 20:48 ` Mark Chambers
2004-10-13 20:54 ` Matt Porter
2004-10-13 21:04 ` Matt Porter
2004-10-13 21:44 ` Mark Chambers
2004-10-13 21:14 ` Eugene Surovegin
2004-10-13 21:18 ` Matt Porter
2004-10-13 21:19 ` Robert P. J. Day
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=Pine.LNX.4.60.0410131453130.13195@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=markc@mail.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 NNTP newsgroup(s).