From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle multiple breakpoint hits in Python interface
Date: Fri, 27 May 2011 20:09:00 -0000 [thread overview]
Message-ID: <m3zkm7ucrb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTik0q4iqSUH9B9ue=0uHzbJqjv32yA@mail.gmail.com> (Kevin Pouget's message of "Mon, 23 May 2011 05:38:54 -0400")
>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:
Kevin> I put back the breakpoint attribute in addition to the "breakpoints"
Kevin> sequence and added in the documentation that it was "legacy support",
Kevin> is it okay for you?
Yes.
Many of your patches seem ready to me. A couple still may need doc
review. IIRC, your paperwork isn't done yet, so at this point we must
wait for that. I don't recall when you sent things in, if it has been a
while you might consider pinging the FSF copyright clerk.
Tom
next prev parent reply other threads:[~2011-05-27 20:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com>
2011-04-22 9:34 ` Kevin Pouget
2011-05-19 18:34 ` Tom Tromey
2011-05-23 9:39 ` Kevin Pouget
2011-05-23 10:51 ` Eli Zaretskii
2011-05-23 11:01 ` Kevin Pouget
2011-05-23 11:59 ` Eli Zaretskii
2011-05-27 20:09 ` Tom Tromey [this message]
2011-05-30 7:37 ` Kevin Pouget
2011-05-30 7:49 ` Eli Zaretskii
2011-05-30 10:53 ` Kevin Pouget
2011-08-31 17:49 ` Tom Tromey
2011-09-01 8:36 ` Kevin Pouget
2011-09-01 8:52 ` Kevin Pouget
2011-09-01 10:08 ` Pedro Alves
2011-09-01 10:18 ` Eli Zaretskii
2011-09-01 11:41 ` Kevin Pouget
2011-09-01 15:39 ` Pedro Alves
2011-09-01 20:53 ` Eli Zaretskii
2011-09-15 12:34 ` Kevin Pouget
2011-09-16 7:55 ` [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface] Jan Kratochvil
2011-09-16 9:12 ` Kevin Pouget
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=m3zkm7ucrb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.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