From: Junio C Hamano <gitster@pobox.com>
To: Yang Zhao <yang.zhao@skyboxlabs.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Emily Shaffer" <emilyshaffer@google.com>,
"Han-Wen Nienhuys" <hanwen@google.com>
Subject: Re: yz/p4-py3, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)
Date: Thu, 13 Feb 2020 20:17:39 -0800 [thread overview]
Message-ID: <xmqqtv3tpzto.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqk14qqj7n.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Thu, 13 Feb 2020 13:18:52 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> So the diff was taken from <20200123175645.GF6837@szeder.dev>; with
> Szeder's SoB (and possibly wordsmithing the log message) let's tie
> this loose end.
Now we are running some tests under py3, we seem to be failing the
tip of 'pu'
https://travis-ci.org/git/git/jobs/650160479
that is getting a SyntaxError.
if message.find(separatorLine) <> -1:
There are other breakages whose causes are already identified in the
recent list messages, e.g.
https://travis-ci.org/git/git/jobs/650160481
is due to a non-portable sed invocation in the bugreport topic,
https://travis-ci.org/git/git/jobs/650160486
is also due to the same topic, and
https://travis-ci.org/git/git/jobs/650160483
is due to the forbidden "for (type var = init; ...)" construct in
new C code.
next prev parent reply other threads:[~2020-02-14 4:17 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtv3tpzto.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--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 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 NNTP newsgroup(s).