From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] windows-nat.c: Handle CTRL_BREAK_EVENT in ctrl_c_handler
Date: Wed, 30 Sep 2009 20:13:00 -0000 [thread overview]
Message-ID: <20090930201338.GA15359@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20090930200927.GA15314@ednor.casa.cgf.cx>
On Wed, Sep 30, 2009 at 04:09:27PM -0400, Christopher Faylor wrote:
>On Tue, Sep 29, 2009 at 04:31:37PM +0200, Pierre Muller wrote:
>> In fact, I double checked,
>>but Chris never answered about the 7 branch...
>
>Huh? You said you committed the CTRL_BREAK_EVENT patch in this thread
>to the gdb_7_0_branch.
>
>If you'r talking about your other patch in another thread, then I'm not
>comfortable with that going into either the trunk or the branch. It
>seems too much like a band-aid.
Ah, sorry. I see. I missed a query. I was ignoring this thread after
the initial approval since it strayed into a discussion the exact right
syntax to use for the documentation.
I have no problems with this going into the branch and actually
mistakenly thought that it was being proposed for both branch and trunk.
cgf
next prev parent reply other threads:[~2009-09-30 20:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 15:24 Pierre Muller
2009-09-21 17:31 ` Eli Zaretskii
2009-09-22 15:35 ` Pierre Muller
2009-09-22 17:58 ` Eli Zaretskii
2009-09-22 18:05 ` Joel Brobecker
2009-09-22 22:02 ` Pierre Muller
2009-09-26 16:49 ` Eli Zaretskii
2009-09-29 7:29 ` Pierre Muller
2009-09-29 14:15 ` Joel Brobecker
2009-09-29 14:33 ` Pierre Muller
2009-09-30 20:09 ` Christopher Faylor
2009-09-30 20:13 ` Christopher Faylor [this message]
2009-09-29 18:55 ` Eli Zaretskii
2009-09-29 21:22 ` Joel Brobecker
2009-09-30 7:42 ` Pierre Muller
2009-09-21 17:37 ` Daniel Jacobowitz
2009-09-21 22:15 ` Christopher Faylor
2009-09-21 22:39 ` Pierre Muller
2009-09-22 15:49 ` Joel Brobecker
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=20090930201338.GA15359@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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