From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [mi] organize possible exec async mi oc command reasons
Date: Sun, 29 May 2005 04:57:00 -0000 [thread overview]
Message-ID: <20050529030004.GC14380@nevyn.them.org> (raw)
In-Reply-To: <20050529025530.GB9122@white>
On Sat, May 28, 2005 at 10:55:30PM -0400, Bob Rossi wrote:
> Oops, here is the 2 new files I forgot to put in the last patch.
You're faster than I am :-) This patch is now OK. Please do me a
favor and add an extra space here:
> /* Represents the reason why GDB is sending an asynchronous command to the
> front end. NOTE: When modifing this, don't forget to update gdb.texinfo! */
^ right there. Might need an extra line after that if
it pushes the end-comment out too far.
Thanks for your perseverance, as usual.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-29 3:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 15:46 Bob Rossi
2005-03-24 15:54 ` Daniel Jacobowitz
2005-03-24 16:06 ` Daniel Jacobowitz
2005-03-24 18:47 ` Stan Shebs
2005-03-24 21:20 ` Bob Rossi
2005-03-26 10:43 ` Eli Zaretskii
2005-04-30 19:32 ` Daniel Jacobowitz
2005-05-18 3:29 ` Bob Rossi
2005-05-18 3:34 ` Daniel Jacobowitz
2005-05-18 3:36 ` Bob Rossi
2005-05-18 3:43 ` Daniel Jacobowitz
2005-05-18 4:00 ` Bob Rossi
2005-05-18 8:53 ` Bob Rossi
2005-05-26 2:35 ` Bob Rossi
2005-05-28 18:56 ` Daniel Jacobowitz
2005-05-29 2:55 ` Bob Rossi
2005-05-29 3:00 ` Bob Rossi
2005-05-29 4:57 ` Daniel Jacobowitz [this message]
2005-05-29 5:53 ` Bob Rossi
2005-05-29 3:11 ` Daniel Jacobowitz
2005-06-15 19:25 ` David Lecomber
2005-06-15 20:03 ` Bob Rossi
2005-06-15 20:46 ` Daniel Jacobowitz
2005-03-24 20:00 ` Eli Zaretskii
2005-03-24 21:02 ` Bob Rossi
2005-03-26 10:40 ` Eli Zaretskii
2005-03-26 13:32 ` Eli Zaretskii
2005-03-27 2:56 ` Bob Rossi
2005-03-27 4:42 ` Eli Zaretskii
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=20050529030004.GC14380@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.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