From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: andrzej zaborowski <balrog@zabor.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] interpreter-exec error path
Date: Fri, 17 Nov 2006 22:49:00 -0000 [thread overview]
Message-ID: <17758.15225.469407.715447@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061117224618.GA18529@nevyn.them.org>
> > Just that you agree to the corresponding change to MI before I submit a
> > patch.
>
> Is it just the behavior of a second command on the interpreter-exec
> line after the first errors? If so, I thought I had already agreed;
> I don't think continuing there is useful.
OK, I'll submit something.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-11-17 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 22:10 Nick Roberts
2006-09-16 4:09 ` Daniel Jacobowitz
2006-09-16 9:36 ` Nick Roberts
2006-11-17 21:17 ` Daniel Jacobowitz
2006-11-17 22:39 ` Nick Roberts
2006-11-17 22:46 ` Daniel Jacobowitz
2006-11-17 22:49 ` Nick Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-11 0:48 andrzej zaborowski
2006-09-16 4:12 ` 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=17758.15225.469407.715447@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=balrog@zabor.org \
--cc=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