On 14.04.17 17:02, Nick Coghlan wrote:
On 12 April 2017 at 01:57, Guido van Rossum wrote:
On Tue, Apr 11, 2017 at 7:42 AM, Nick Coghlan wrote:
Since we do the squash & merge to get an atomic commit at the end, it
doesn't make sense to do any force pushes along the way.
I was going to argu
Hi,
If you've been using cherry_picker.py, please update it ( by doing `git
pull` ).
With this update, the branch number is automatically prefixed in the commit
message. (https://github.com/python/core-workflow/issues/44)
Added --abort/--continue options to address
https://github.com/python/core
On 15 April 2017 at 03:15, Serhiy Storchaka wrote:
> On 14.04.17 17:02, Nick Coghlan wrote:
>> That was exactly my reaction when Serhiy pointed it out - I started to
>> argue the point, but then invalidated all my own arguments before
>> actually posting anything :)
>
> I don't remember I said any
On 15 April 2017 at 11:24, Mariatta Wijaya wrote:
> Hi,
>
> If you've been using cherry_picker.py, please update it ( by doing `git
> pull` ).
>
> With this update, the branch number is automatically prefixed in the commit
> message. (https://github.com/python/core-workflow/issues/44)
>
> Added --
On 12 April 2017 at 01:57, Guido van Rossum wrote:
> On Tue, Apr 11, 2017 at 7:42 AM, Nick Coghlan wrote:
>>
>> Since we do the squash & merge to get an atomic commit at the end, it
>> doesn't make sense to do any force pushes along the way.
>
>
> I was going to argue with this, but then I realiz
