From: Eli Zaretskii <eliz@gnu.org>
To: Justin Lebar <justin.lebar@gmail.com>
Cc: dje@google.com, stanshebs@earthlink.net, gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Tue, 25 Oct 2011 16:53:00 -0000 [thread overview]
Message-ID: <83ipndc92n.fsf@gnu.org> (raw)
In-Reply-To: <CAFWcpZ6JtXqu3W9A05CO5ZuAxYGev8W_-kUsGOZWDB5Y+2JuOA@mail.gmail.com>
> From: Justin Lebar <justin.lebar@gmail.com>
> Date: Tue, 25 Oct 2011 12:08:09 -0400
> Cc: dje@google.com, stanshebs@earthlink.net, gdb-patches@sourceware.org
>
> > What happens if I have a function called "file" in the same program?
> > IOW, to what degree is "file" a reserved keyword here?
>
> Even if you have a function named "file", |skip file| will skip the
> current file. But |skip function file| would skip the function called
> "file".
I suggest to say this explicitly as a note. E.g., like this:
(If you have a function called @code{file} that you want to skip, use
@kbd{skip function file} to specify it.)
> >> +@item Type
> >> +@samp{function} or @samp{file}
> >
> > The text below the @item line should be at least one complete
> > sentence.
>
> FWIW, I think
>
> @samp{function} or @samp{file}
>
> beats
>
> This field contains either @samp{function} or @samp{file},
> indicating whether
> the skip is on one function or all the functions in a file.
I didn't suggest the latter; you did ;-)
I will settle for
The type of this skip, either @samp{function} or @samp{file}.
> > @item Identifier
> > A number identifying this skip.
>
> This is not a complete sentence. Should it be changed as well?
No need, it is complete enough for me.
Thanks.
next prev parent reply other threads:[~2011-10-25 16:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51 ` Stan Shebs
2011-10-06 20:16 ` Justin Lebar
2011-10-10 12:34 ` Stan Shebs
2011-10-11 21:34 ` Justin Lebar
2011-10-11 23:54 ` Doug Evans
2011-10-16 19:22 ` Justin Lebar
2011-10-20 19:46 ` Tom Tromey
2011-10-25 20:07 ` Justin Lebar
2011-10-25 20:41 ` Pedro Alves
2011-10-25 21:25 ` Justin Lebar
2011-10-20 20:40 ` Eli Zaretskii
2011-10-25 16:47 ` Justin Lebar
2011-10-25 16:53 ` Eli Zaretskii [this message]
2011-10-25 19:52 ` Justin Lebar
2011-10-25 20:13 ` Eli Zaretskii
2011-10-25 20:30 ` Justin Lebar
2011-10-26 1:06 ` Stan Shebs
2011-10-26 3:45 ` Justin Lebar
2011-10-26 5:37 ` Stan Shebs
2011-10-26 8:10 ` Joel Brobecker
2011-10-26 13:28 ` Eli Zaretskii
2011-10-26 15:11 ` Justin Lebar
2011-10-28 18:18 ` Tom Tromey
2011-10-28 19:48 ` Justin Lebar
2011-10-28 19:53 ` Tom Tromey
2011-10-28 19:49 ` Tom Tromey
2011-10-28 19:55 ` Justin Lebar
2011-10-28 20:37 ` Tom Tromey
2011-10-31 15:52 ` Justin Lebar
[not found] ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53 ` Justin Lebar
2011-11-02 22:43 ` Maciej W. Rozycki
2011-11-02 23:52 ` Stan Shebs
2011-11-03 0:20 ` Maciej W. Rozycki
2011-11-03 3:54 ` Eli Zaretskii
2011-11-03 14:32 ` Tom Tromey
2011-11-03 16:54 ` Eli Zaretskii
2011-11-03 18:04 ` Maciej W. Rozycki
2011-11-03 18:25 ` Eli Zaretskii
2011-11-03 19:01 ` Stan Shebs
2011-10-06 17:19 ` Diego Novillo
2011-10-06 17:33 ` Tom Tromey
2011-10-06 17:37 ` Diego Novillo
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=83ipndc92n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=justin.lebar@gmail.com \
--cc=stanshebs@earthlink.net \
/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