From: Keith Seitz <keiths@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Delayed physnames, revisited
Date: Fri, 20 Aug 2010 17:17:00 -0000 [thread overview]
Message-ID: <4C6EB87E.7070200@redhat.com> (raw)
In-Reply-To: <AANLkTinRszypTZJ2WZ2rAH15ZqUh5CjP5cirr=kGQrAD@mail.gmail.com>
On 08/19/2010 04:25 PM, Doug Evans wrote:
> Folks are great at enforcing things like putting a space after the
> function name in a function call, but not so good at enforcing having
> a blank line between a function's comment and definition.
>
> Keith, can you fix that?
Committed with that trivial change.
Thanks Tom and Doug!
Keith
next prev parent reply other threads:[~2010-08-20 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 21:01 Keith Seitz
2010-08-19 19:36 ` Tom Tromey
2010-08-19 23:26 ` Doug Evans
2010-08-20 17:17 ` Keith Seitz [this message]
2010-08-22 18:46 ` New UNRESOLVED testcase gdb.dwarf2/dw2-double-set-die-type.exp [Re: [RFA] Delayed physnames, revisited] Jan Kratochvil
2010-08-23 19:13 ` Keith Seitz
2010-08-20 17:50 ` [RFA] Delayed physnames, revisited Thiago Jung Bauermann
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=4C6EB87E.7070200@redhat.com \
--to=keiths@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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