From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gdb-mi.el
Date: Sat, 25 Mar 2006 10:14:00 -0000 [thread overview]
Message-ID: <u64m354ex.fsf@gnu.org> (raw)
In-Reply-To: <17444.61028.687335.767627@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 25 Mar 2006 19:16:52 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 25 Mar 2006 19:16:52 +1200
>
> Here's my latest patch for gdb-mi.el. I guess it's a little bit pointless as
> Emacs doesn't seem to have a slow release cycle, so much as a no release cycle
> - its just to keep things tidy.
>
> OK to commit?
Yes.
next prev parent reply other threads:[~2006-03-25 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 8:19 Nick Roberts
2006-03-25 10:14 ` Eli Zaretskii [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-02-10 4:02 Nick Roberts
2006-02-10 5:34 ` Daniel Jacobowitz
2006-02-10 6:22 ` Nick Roberts
2005-11-14 11:34 Nick Roberts
2005-11-17 10:04 ` Daniel Jacobowitz
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=u64m354ex.fsf@gnu.org \
--to=eliz@gnu.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