From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove unused exp_opcodes
Date: Tue, 01 Jun 2010 22:25:00 -0000 [thread overview]
Message-ID: <m3zkze4chg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100601215926.GU3019@adacore.com> (Joel Brobecker's message of "Tue, 1 Jun 2010 14:59:26 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> I'll confess that I am not quite sure whether you're supposed to close
Joel> the '<' at the end of the line, or whether it can continue on the next
Joel> line like you did. I don't think it's a huge deal, but we can fix that
Joel> if someone knows and it turns out to be wrong...
I wouldn't worry about it at all.
As long as the names are spelled right I don't think the details of the
syntax matter.
Tom
next prev parent reply other threads:[~2010-06-01 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 21:37 Sergio Durigan Junior
2010-06-01 21:59 ` Joel Brobecker
2010-06-01 22:25 ` Tom Tromey [this message]
2010-06-02 0:41 ` Sergio Durigan Junior
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=m3zkze4chg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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