From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: el vs ell (Re: Static tracepoints support)
Date: Thu, 01 Jul 2010 16:26:00 -0000 [thread overview]
Message-ID: <4C2CC1A0.50502@vmware.com> (raw)
In-Reply-To: <201007011449.54153.pedro@codesourcery.com>
Pedro Alves wrote:
> On Monday 28 June 2010 13:26:38, Pedro Alves wrote:
>>>> +query), until the target responds with @samp{l} (lower-case el, for
>>>> +@dfn{last}). ^^
>>> "ell"
>> Thanks. This was copied from elsewhere. I'll audit those as well
>> after this is in.
>>
>
> As promised.. There is only one other instance of "el" or "ell" in
> the manuals or sources I could find (cd gdb; egrep " el(l)?(,|\.| )" * -rn),
> and it was the one I copied from. I was going to fix it, but, I noticed
> that <http://en.wikipedia.org/wiki/L> says:
>
> "L is the twelfth letter of the basic modern Latin alphabet. Its name in
> English (play /ˈɛl/) is spelled el or occasionally ell.[1]"
>
> So, which one should we use? Is this an American English vs other
> flavours issue?
>
You could just say "lower-case 'L'"...
next prev parent reply other threads:[~2010-07-01 16:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 18:33 Static tracepoints support Pedro Alves
2010-06-26 10:34 ` Eli Zaretskii
2010-06-28 12:28 ` Pedro Alves
2010-06-28 20:03 ` Eli Zaretskii
2010-06-29 21:00 ` Pedro Alves
2010-06-30 18:14 ` Eli Zaretskii
2010-07-01 10:41 ` Pedro Alves
2010-07-01 14:22 ` clarify "help break" output a bit (Re: Static tracepoints support) Pedro Alves
2010-07-01 17:10 ` Eli Zaretskii
2010-06-28 20:04 ` Static tracepoints support Eli Zaretskii
2010-07-01 13:50 ` el vs ell (Re: Static tracepoints support) Pedro Alves
2010-07-01 16:26 ` Michael Snyder [this message]
2010-07-01 17:07 ` Eli Zaretskii
2010-07-01 17:28 ` Pedro Alves
2010-07-01 14:00 ` Static tracepoints support Pedro Alves
2010-07-01 17:08 ` Eli Zaretskii
2010-07-01 17:13 ` Pedro Alves
2010-07-01 14:15 ` add a few index entries (Re: Static tracepoints support) Pedro Alves
2010-07-01 17:09 ` Eli Zaretskii
2010-07-01 15:38 ` remove redundant blank from strings " Pedro Alves
2010-07-01 17:11 ` Eli Zaretskii
2010-07-01 16:36 ` dynamic type column width in "info breakpoints" output " Pedro Alves
2010-07-01 17:17 ` Eli Zaretskii
2010-07-02 21:35 ` Tom Tromey
2010-07-21 11:30 ` Pedro Alves
2010-06-27 22:47 ` Static tracepoints support Michael Snyder
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=4C2CC1A0.50502@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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).