According to the logs it's been fixed.
On Fri, Jun 3, 2016 at 7:32 PM, Jesus Cea wrote:
> On 03/06/16 23:50, R. David Murray wrote:
>> I don't understand how it happened, but apparently I got a merge commit
>> backward and merged 3.6 into 3.5 and pushed it without realizing what
>>
On 03/06/16 23:50, R. David Murray wrote:
> I don't understand how it happened, but apparently I got a merge commit
> backward and merged 3.6 into 3.5 and pushed it without realizing what
> had happened. If anyone has any clue how to reverse this cleanly,
> please let me know. (There are a
I don't understand how it happened, but apparently I got a merge commit
backward and merged 3.6 into 3.5 and pushed it without realizing what
had happened. If anyone has any clue how to reverse this cleanly,
please let me know. (There are a couple people at the sprints looking
in to it, but the
Le 2 juin 2016 20:32, "Antoine Pitrou" a écrit :
>
>
> Le 02/06/2016 20:26, Brett Cannon a écrit :
> >
> > 1. Have him send me his preferred email address for python-committers
> > 2. Make sure he has his github username listed on bugs.python.org
> >