From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] remote-mips.c: Make sure that each function has an introductory comment
Date: Wed, 10 Mar 2010 17:08:00 -0000 [thread overview]
Message-ID: <83fx482jfv.fsf@gnu.org> (raw)
In-Reply-To: <20100309223707.4ea02d43@redhat.com>
> Date: Tue, 9 Mar 2010 22:37:07 -0700
> From: Kevin Buettner <kevinb@redhat.com>
>
> On Tue, 09 Mar 2010 19:50:05 +0200
> Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Thanks for working on this.
>
> Thanks for taking the time to look it over.
>
> Below is a new patch which, I hope, addresses your concerns.
It does, thanks.
next prev parent reply other threads:[~2010-03-10 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:18 Kevin Buettner
2010-03-09 5:25 ` Joel Brobecker
2010-03-09 17:50 ` Eli Zaretskii
2010-03-10 5:37 ` Kevin Buettner
2010-03-10 17:08 ` Eli Zaretskii [this message]
2010-03-11 3:48 ` Kevin Buettner
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=83fx482jfv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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