From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA/RFC/DOC] Fix the different between behavior of "detach inferior" "kill inferior" and doc
Date: Fri, 30 Jul 2010 14:57:00 -0000 [thread overview]
Message-ID: <AANLkTinMzgCLj_TVPstyATGiBRU37_-GP9zNy6Cf+gQg@mail.gmail.com> (raw)
In-Reply-To: <201007301057.11965.pedro@codesourcery.com>
7.2 and head checked in.
Thanks,
Hui
On Fri, Jul 30, 2010 at 17:57, Pedro Alves <pedro@codesourcery.com> wrote:
> On Friday 30 July 2010 10:02:06, Hui Zhu wrote:
>> Joel, do you think 7.2 need this patch?
>
> It's clearly a no-risk patch, assuming it doesn't break
> regenerating the docs, and makes the docs match the
> real behavior, so, if you'll willing to apply it, then
> please go ahead.
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2010-07-30 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 8:14 Hui Zhu
2010-07-30 8:45 ` Eli Zaretskii
2010-07-30 9:02 ` Hui Zhu
2010-07-30 9:57 ` Pedro Alves
2010-07-30 14:57 ` Hui Zhu [this message]
2010-07-30 9:38 ` Pedro Alves
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=AANLkTinMzgCLj_TVPstyATGiBRU37_-GP9zNy6Cf+gQg@mail.gmail.com \
--to=teawater@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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