[patch] [python] Implement Inferior.current_inferior

Phil Muldoon pmuldoon@redhat.com
Tue Jun 28 08:20:00 GMT 2011


Kevin Pouget <kevin.pouget@gmail.com> writes:

> Hi,
>
> sorry for the troubles, I'll assign the patches to myself next times!

That's ok, like I mentioned I did not do it for this bug either!  But
assignments do avoid issues like these.  As it happens I spent most of
the time with the patch fixing the reference counting buglets.  So go
ahead and assign yourself whatever bugs you are working on now.  When
you get your FSF paperwork sorted generally, and maintainer approval for
each patch, make sure you put the bug number in the ChangeLog (look for
other examples of this), and close the bug with the target milestone set
for the expected release of this patch (e.g. 7.4).

> the patch was reviewed and accepted,

Ok, then lets do this.  You wrote the patch, it was reviewed and
accepted so your patch should go in. This functionality is targeted
for 7.4 and so that is quite a long time away. You will (hopefully) have
FSF assignment sorted by then!  I'll break out the reference counting
fixes and submit it as a separate patch.  This is important as
selected_inferior will crash on short lived anonymous references.  The
two patches should come together nicely, then.


Does this sound okay to you?

Thanks again for all your work, Kevin.

Cheers,

Phil



More information about the Gdb-patches mailing list