Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Cc: Nick Roberts <nickrob@snap.net.nz>
Subject: Re: [RFC] Fix MI timings
Date: Fri, 13 Mar 2009 07:59:00 -0000	[thread overview]
Message-ID: <200903130853.30925.vladimir@codesourcery.com> (raw)
In-Reply-To: <200903100032.25610.vladimir@codesourcery.com>

On Tuesday 10 March 2009 00:32:25 Vladimir Prus wrote:

> > Also, since this is public, please give it an "mi_" prefix.
> >
> > I have nothing useful to say about the important part of the patch,
> > though.
>
> OK :-) Here's a revised patch, just in case.

I've checked it in.

- Volodya


      parent reply	other threads:[~2009-03-13  5:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 21:10 Vladimir Prus
2009-03-09 21:15 ` Vladimir Prus
2009-03-09 21:22   ` Daniel Jacobowitz
2009-03-09 21:32     ` Vladimir Prus
2009-03-09 21:36       ` Pedro Alves
2009-03-09 22:07         ` Pedro Alves
2009-03-17  5:27         ` Pedro Alves
2009-03-17  7:26           ` Vladimir Prus
2009-03-17  8:03             ` Vladimir Prus
2009-03-13  7:59       ` Vladimir Prus [this message]

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=200903130853.30925.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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