From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, Yang Zhao <yang.zhao@skyboxlabs.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: yz/p4-py3, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)
Date: Tue, 10 Mar 2020 11:29:21 -0700 [thread overview]
Message-ID: <xmqq7dzsjc72.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200310173835.GC3122@szeder.dev> ("SZEDER Gábor"'s message of "Tue, 10 Mar 2020 18:38:35 +0100")
SZEDER Gábor <szeder.dev@gmail.com> writes:
> Here is the SoB and the wordsmithed commit message.
> ...
> Subject: [PATCH] ci: use python3 in linux-gcc and osx-gcc and python2 elsewhere
>
> Python2 reached end of life, and we have been preparing our Python
> scripts to work with Python3. 'git p4', the main in-tree user of
> Python, has just received a number of compatibility updates. Our
> other notable Python script 'contrib/svn-fe/svnrdump_sim.py' is only
> used in 't9020-remote-svn.sh', and is apparently already compatible
> with both Python2 and 3.
>
> Our CI jobs currently only use Python2. We want to make sure that
> these Python scripts do indeed work with Python3, and we also want to
> make sure that these scripts keep working with Python2 as well, for
> the sake of some older LTS/Enterprise setups.
>
> Therefore, pick two jobs and use Python3 there, while leaving other
> jobs to still stick to Python2 for now.
>
> Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nicely written. Thanks.
next prev parent reply other threads:[~2020-03-10 18:29 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7dzsjc72.fsf@gitster.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.