> Modifying GitHub Labels is only available to people with commit privs and,
> IIRC, Skip asked to drop his commit privs a few years ago (although I'm sure
> we would all be happy to welcome him back!).
Alas, then I would feel some obligation to be semi-responsive to buggy
things in areas where
> You created the PR from your local python repository master branch. I have
> done this, with negative consequences. I believe you will find life with
> git easier if you never edit your master branch, or at least, never make
> local commits to it, and only commit to and create PRs from special-
On Apr 5, 2018, at 14:48, Terry Reedy wrote:
> On 4/5/2018 5:47 AM, Skip Montanaro wrote:
>>> There are a bunch of open issues regarding gdb support including one with a
>>> PR in need of review for 3.6+.
>> I rejected one (which assumed everyone now uses a python-aware gdb),
>> commented on anot
On 4/5/2018 5:47 AM, Skip Montanaro wrote:
There are a bunch of open issues regarding gdb support including one with a PR
in need of review for 3.6+.
I rejected one (which assumed everyone now uses a python-aware gdb),
commented on another (ceval.c-related name changes in several
commands), an
On Apr 5, 2018, at 12:35, Brett Cannon wrote:
> On Thu, 5 Apr 2018 at 02:49 Skip Montanaro wrote:
>> > There are a bunch of open issues regarding gdb support including one with
>> > a PR in need of review for 3.6+.
>>
>> I rejected one (which assumed everyone now uses a python-aware gdb),
>> co
On Thu, 5 Apr 2018 at 02:49 Skip Montanaro wrote:
> > There are a bunch of open issues regarding gdb support including one
> with a PR in need of review for 3.6+.
>
> I rejected one (which assumed everyone now uses a python-aware gdb),
> commented on another (ceval.c-related name changes in sever
> There are a bunch of open issues regarding gdb support including one with a
> PR in need of review for 3.6+.
I rejected one (which assumed everyone now uses a python-aware gdb),
commented on another (ceval.c-related name changes in several
commands), and created a PR for third (documentation fo
There are a bunch of open issues regarding gdb support including one with a PR
in need of review for 3.6+. I imagine that there are duplicates at least among
the more recent open issues. If you use and are familiar with the gdb macros,
it would be really swell if you could take some time to re
