From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Don't kill inferior if there's a typo in the specified port.
Date: Thu, 30 Apr 2009 22:16:00 -0000 [thread overview]
Message-ID: <200904302316.23307.pedro@codesourcery.com> (raw)
In-Reply-To: <e394668d0904301451q3b23dc91yfec9f428b537a2ba@mail.gmail.com>
On Thursday 30 April 2009 22:51:27, Doug Evans wrote:
> >>> Ok to check in?
> >>
> >> This is fine with me. Let's give it a few days in case Daniel or
> >> others want to comment.
> >>
> >> Thanks for documenting detach_or_kill_inferior_callback, btw ;-).
> >>
> >> --
> >> Pedro Alves
> >>
> >
> Ok to check this in?
Eh, I thought we had already settled. :-)
> It does
>
> Killing process(es) PID1, PID2, PID3, PID4, PIDnn.
> Detaching process(es) PID1, PID2, PID3, PID4, PIDnn.
>
> though I removed the commas for simplicity.
> [I'm proactively avoiding some of the issues being raised. :-)]
It looks fine to me. Please go ahead before someone has a
different idea. :-) Thanks!
--
Pedro Alves
prev parent reply other threads:[~2009-04-30 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 23:18 Doug Evans
2009-04-11 15:03 ` Pedro Alves
2009-04-13 18:49 ` Doug Evans
2009-04-30 21:51 ` Doug Evans
2009-04-30 22:16 ` Pedro Alves [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=200904302316.23307.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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