Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gdb-mi.el
Date: Thu, 17 Nov 2005 10:04:00 -0000	[thread overview]
Message-ID: <20051117035729.GE3057@nevyn.them.org> (raw)
In-Reply-To: <17272.3578.497649.130924@kahikatea.snap.net.nz>

On Mon, Nov 14, 2005 at 05:09:30PM +1300, Nick Roberts wrote:
> 
> Here's another patch for gdb-mi.el.  OK to commit to mainline and release
> branch?

Yes, please do.


-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-17  3:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 11:34 Nick Roberts
2005-11-17 10:04 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-22 21:04 Nick Roberts
2006-08-22 21:32 ` Daniel Jacobowitz
2006-05-14 13:28 Nick Roberts
2006-05-14 20:07 ` Eli Zaretskii
2006-03-25  8:19 Nick Roberts
2006-03-25 10:14 ` Eli Zaretskii
2006-02-10  4:02 Nick Roberts
2006-02-10  5:34 ` Daniel Jacobowitz
2006-02-10  6:22   ` Nick Roberts
2005-10-27 12:10 Nick Roberts
2005-10-27 16:54 ` 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=20051117035729.GE3057@nevyn.them.org \
    --to=drow@false.org \
    --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