From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: PR 2484: completion of macro names
Date: Tue, 30 Sep 2008 17:25:00 -0000 [thread overview]
Message-ID: <m38wt9o8i9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200809301753.49962.pedro@codesourcery.com> (Pedro Alves's message of "Tue\, 30 Sep 2008 17\:53\:49 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>> + /* Style of macro expansion, if any, supported by this language. */
>> + enum macro_expansion la_macro_expansion : 1;
Pedro> Left over ` : 1'.
Thanks, I fixed this.
Pedro> Looks OK to me. Thanks again for doing this.
I checked it in.
Tom
next prev parent reply other threads:[~2008-09-30 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:39 Tom Tromey
2008-07-29 20:49 ` regression test on the compile farm Thiago Jung Bauermann
2008-07-29 21:39 ` Tom Tromey
2008-09-28 22:01 ` RFA: PR 2484: completion of macro names Pedro Alves
2008-09-30 16:13 ` Tom Tromey
2008-09-30 16:54 ` Pedro Alves
2008-09-30 17:25 ` Tom Tromey [this message]
2008-10-01 17:46 ` Tom Tromey
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=m38wt9o8i9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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