From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
Mark Wielaard <mark@klomp.org>,
gbenson@redhat.com
Subject: Re: [RFA take 6] Allow setting breakpoints on inline functions (PR 10738)
Date: Wed, 14 Mar 2012 17:58:00 -0000 [thread overview]
Message-ID: <CADPb22S8992GZdoP7x_o897bWhrzS5Cz9_agM_ThVRXpEDm3bA@mail.gmail.com> (raw)
In-Reply-To: <20120314175451.GA20072@host2.jankratochvil.net>
On Wed, Mar 14, 2012 at 10:54 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 14 Mar 2012 18:50:55 +0100, Doug Evans wrote:
>> + --use-old-index-sections\n\
>> + Do not reject old (broken) .gdb_index sections.\n\
>> +"), stream);
>>
>> s/(broken)/(incomplete)/
>
> FYI I may not have the right interpretation of English words but with
> "incomplete" it may suggest to me that only part of the file will use index
> and part of the file will be processed by a slower non-indexed method.
>
> It should suggest user the GDB functionality will be affected.
The doc patch uses the word "incomplete", so that's why I suggest using it here.
If one wants to find a better word, great, but I think the same word
should be used in both places.
next prev parent reply other threads:[~2012-03-14 17:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 13:38 Gary Benson
2012-03-14 17:51 ` Doug Evans
2012-03-14 17:55 ` Jan Kratochvil
2012-03-14 17:58 ` Doug Evans [this message]
2012-03-15 10:51 ` Gary Benson
2012-03-15 10:52 ` Jan Kratochvil
2012-03-15 16:51 ` Doug Evans
2012-03-15 18:04 ` Eli Zaretskii
2012-03-15 18:10 ` Gary Benson
2012-03-15 18:15 ` Eli Zaretskii
2012-03-15 18:26 ` Gary Benson
2012-03-15 18:31 ` Pedro Alves
2012-03-15 18:36 ` Eli Zaretskii
2012-03-15 18:40 ` Jan Kratochvil
2012-03-15 19:29 ` Gary Benson
2012-03-15 19:34 ` Doug Evans
2012-03-15 19:52 ` Pedro Alves
2012-03-15 20:06 ` Pedro Alves
2012-03-16 10:03 ` Gary Benson
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=CADPb22S8992GZdoP7x_o897bWhrzS5Cz9_agM_ThVRXpEDm3bA@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark@klomp.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