Re: yz/p4-py3, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:

> On Wed, 12 Feb 2020, Junio C Hamano wrote:
>
>> * yz/p4-py3 (2020-01-15) 14 commits
>>  . ci: also run linux-gcc pipeline with python3.5 environment
>>  - git-p4: use python3's input() everywhere
>>  ...
>>
>>  Update "git p4" to work with Python 3.
>>
>>  Hold.
>>  The last step is too wasteful to run full tests twice.
>>  cf. <20200122235333.GA6837@xxxxxxxxxx>
>>  cf. <20200123175645.GF6837@xxxxxxxxxx>
>
> All right, all right, all right! If we cannot find any better way than to
> just use Python2 in -clang and Python3 in -gcc (or was it the other way
> round, I forget), then we cannot find any better way, and I won't hold
> this up any longer.

OK, any one of you wants to do the honors of wrapping up the
proposed patch with a log message to replace the tip commit to allow
us to move forward?

Thanks.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux