From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@sebabeach.org>, msnyder@vmware.com
Subject: Re: [RFA] target record_core -> target record-core?
Date: Tue, 20 Apr 2010 09:56:00 -0000 [thread overview]
Message-ID: <201004201056.12467.pedro@codesourcery.com> (raw)
In-Reply-To: <20100419064717.75D476E3DC@sebabeach.org>
FWIW, I agree with this,
On Monday 19 April 2010 07:47:17, Doug Evans wrote:
> 2010-04-18 Doug Evans <dje@sebabeach.org>
>
> * record.c (init_record_core_ops): Rename record_core to record_core.
though the log entry mentions a nop. :-)
--
Pedro Alves
next prev parent reply other threads:[~2010-04-20 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 6:47 Doug Evans
2010-04-19 18:01 ` Michael Snyder
2010-04-20 9:56 ` Pedro Alves [this message]
2010-04-20 12:24 ` Hui Zhu
2010-04-20 18:06 ` Tom Tromey
2010-04-20 18:11 ` Joel Brobecker
2010-04-23 20:40 ` Patch: completion -vs- deprecated commands (Was: [RFA] target record_core -> target record-core?) Tom Tromey
2010-04-26 18:37 ` Patch: completion -vs- deprecated commands 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=201004201056.12467.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@sebabeach.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).