From: Phil Muldoon <pmuldoon@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [python] Implement Inferior.current_inferior
Date: Mon, 27 Jun 2011 19:30:00 -0000 [thread overview]
Message-ID: <m3k4c79inv.fsf@redhat.com> (raw)
In-Reply-To: <BANLkTimA=NDWjafwkWzxEWPEBt9qZ_Dfww@mail.gmail.com> (Kevin Pouget's message of "Mon, 27 Jun 2011 19:34:04 +0200")
Kevin Pouget <kevin.pouget@gmail.com> writes:
> Hi,
>
> I actually proposed and got approved a patch to solve this bug two months ago,
>
> http://sources.redhat.com/ml/gdb-patches/2011-04/msg00389.html
>
> but I'm still waiting for these crazy copyright assignment papers to
> cross the ocean, it looks like that they won't never reach the old
> continent, too bad ...
Ping the maintainers and see if they can rattle some FSF folks into
action.
I do not mind which patch fixes the issues. But please assign a bug to
yourself if you are working on it, so we don't duplicate effort. (On
that note, I did not assign it to myself yet either so touche).
Whether your patch, or mine makes it in I don't mind. The patches looks
similar, but mine has a few extra tests and accounts for the reference
leaking/sigsegv. I would be happy to add your name to the ChangeLog as
co-implementer if the maintainers think this is ok (and they approve the
patch).
Cheers,
Phil
next prev parent reply other threads:[~2011-06-27 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 14:11 Phil Muldoon
2011-06-27 17:35 ` Kevin Pouget
2011-06-27 19:30 ` Phil Muldoon [this message]
2011-06-27 20:13 ` Joel Brobecker
2011-06-27 20:27 ` Phil Muldoon
2011-06-28 7:47 ` Kevin Pouget
2011-06-28 8:20 ` Phil Muldoon
2011-06-28 20:31 ` Tom Tromey
2011-06-28 20:30 ` Tom Tromey
2011-06-28 22:14 ` Phil Muldoon
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=m3k4c79inv.fsf@redhat.com \
--to=pmuldoon@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