From: Chris Genly <chgenly@gmail.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI register groups
Date: Mon, 15 Jun 2009 18:48:00 -0000 [thread overview]
Message-ID: <ed4903890906151142j5350c39ay5af7e4fb82c084e9@mail.gmail.com> (raw)
In-Reply-To: <h1646i$okb$1@ger.gmane.org>
Oh a development list. That sounds better. I'll switch over. I
didn't see that list when I went looking for it. Here is where I
looked. http://www.gnu.org/software/gdb/mailing-lists/
http://www.gnu.org/software/gdb/mailing-lists/
On Mon, Jun 15, 2009 at 11:33 AM, Vladimir Prus
<vladimir@codesourcery.com> wrote:
>
> Well, gdb-devel@. In practice, I am most likely to comment on any MI
> proposals.
>
> - Volodya
>
>
next prev parent reply other threads:[~2009-06-15 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 18:10 Chris Genly
2009-06-15 18:25 ` Marc Khouzam
2009-06-15 18:43 ` Chris Genly
[not found] ` <ed4903890906151141w1300057g98606b5a3a38fbe2@mail.gmail.com>
2009-06-15 18:44 ` Marc Khouzam
2009-06-15 18:34 ` Vladimir Prus
2009-06-15 18:48 ` Chris Genly [this message]
2009-06-15 19:22 ` Vladimir Prus
2009-06-15 19:25 ` Chris Genly
2009-06-15 20:18 ` Daniel Jacobowitz
2009-06-15 18:34 ` Daniel Jacobowitz
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=ed4903890906151142j5350c39ay5af7e4fb82c084e9@mail.gmail.com \
--to=chgenly@gmail.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@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