git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, "Yang Zhao" <yang.zhao@skyboxlabs.com>,
	"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: yz/p4-py3, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)
Date: Thu, 13 Feb 2020 08:06:49 -0800	[thread overview]
Message-ID: <xmqq7e0qtqsm.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002131401130.46@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Thu, 13 Feb 2020 14:02:23 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> 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@szeder.dev>
>>  cf. <20200123175645.GF6837@szeder.dev>
>
> 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.


  reply	other threads:[~2020-02-13 16:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 21:58 What's cooking in git.git (Feb 2020, #03; Wed, 12) Junio C Hamano
2020-02-13 12:26 ` bw/remote-rename-update-config, was " Johannes Schindelin
2020-02-13 13:02 ` yz/p4-py3, " Johannes Schindelin
2020-02-13 16:06   ` Junio C Hamano [this message]
2020-02-13 21:18     ` Junio C Hamano
2020-02-14  4:17       ` Junio C Hamano
2020-02-14  5:15         ` Denton Liu
2020-02-14 14:39           ` Ben Keene
2020-02-14 16:18             ` Junio C Hamano
2020-02-14 17:01             ` Junio C Hamano
2020-02-14 17:05               ` Ben Keene
2020-02-14 18:10                 ` Junio C Hamano
2020-03-10 17:38       ` SZEDER Gábor
2020-03-10 18:29         ` Junio C Hamano
2020-02-16  4:42 ` Elijah Newren
2020-02-17  7:38   ` Pratyush Yadav

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq7e0qtqsm.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=szeder.dev@gmail.com \
    --cc=yang.zhao@skyboxlabs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).