From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: el vs ell (Re: Static tracepoints support)
Date: Thu, 01 Jul 2010 17:28:00 -0000 [thread overview]
Message-ID: <201007011828.03627.pedro@codesourcery.com> (raw)
In-Reply-To: <83r5jn9ljm.fsf@gnu.org>
On Thursday 01 July 2010 18:09:01, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Thu, 1 Jul 2010 14:49:53 +0100
> > Cc: Eli Zaretskii <eliz@gnu.org>
> >
> > 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?
>
> I don't know about flavors, but every instance I saw used "ell".
>
googling for "lowercase el", I see a bunch. In fact aproximatly
50/50 vs ell. Anyway, I've applied the patch below to make us
use ell in both cases.
On Thursday 01 July 2010 17:26:08, Michael Snyder wrote:
> You could just say "lower-case 'L'"...
the sentense in question goes:
"with l (lower-case ell, for last)"
--
Pedro Alves
2010-07-01 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (General Query Packets) <qfThreadInfo,
qsThreadInfo>: Spell out `l' as ell.
---
gdb/doc/gdb.texinfo | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo 2010-07-01 18:19:10.000000000 +0100
+++ src/gdb/doc/gdb.texinfo 2010-07-01 18:20:07.000000000 +0100
@@ -31744,7 +31744,7 @@ In response to each query, the target wi
more thread IDs, separated by commas.
@value{GDBN} will respond to each reply with a request for more thread
ids (using the @samp{qs} form of the query), until the target responds
-with @samp{l} (lower-case el, for @dfn{last}).
+with @samp{l} (lower-case ell, for @dfn{last}).
Refer to @ref{thread-id syntax}, for the format of the @var{thread-id}
fields.
next prev parent reply other threads:[~2010-07-01 17:28 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
2010-07-01 17:07 ` Eli Zaretskii
2010-07-01 17:28 ` Pedro Alves [this message]
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=201007011828.03627.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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