From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Yang Zhao <yang.zhao@skyboxlabs.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Git Users" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jan 2020, #04; Wed, 22)
Date: Sat, 25 Jan 2020 01:13:52 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2001250112171.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CABvFv3+OfzK_2Wo97dusaj5nomSJTNghJHJa3=+HKH=-Sw12qQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Hi yang,
On Fri, 24 Jan 2020, Yang Zhao wrote:
> On Thu, Jan 23, 2020 at 12:52 PM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > SZEDER Gábor <szeder.dev@gmail.com> writes:
> >
> > > Replacing that last patch of the series with the diff below works both
> > > on Linux and macOS and both on Travis CI and Azure Pipelines.
> > >...
> >
> > Yang, care to do the honors to wrap it up with summary of the
> > decisions as a replacement patch for the last step?
>
> I've done a new rebase on master, did the CI change as discussed, and
> pushed the changes to the GitHub PR
> (https://github.com/git/git/pull/673). osx-gcc test seems to have
> failed something unrelated to these changes, but everything else still
> passes.
This is our good old friend, the flaky test case
t5516.81 deny fetch unreachable SHA1, allowtipsha1inwant=false
It has been discussed before, and it seems that Gábor has a patch that
works, but that he is not completely happy with, yet.
I restarted the job, it should turn green in about 20-25 minutes.
Thanks,
Dscho
>
> The changes I've had to make to make it merge were minimal. I can send
> a new revision to the list later today if that's more convenient.
>
> Thanks,
> --
> yang
>
next prev parent reply other threads:[~2020-01-25 0:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 22:18 What's cooking in git.git (Jan 2020, #04; Wed, 22) Junio C Hamano
2020-01-22 22:37 ` Elijah Newren
2020-01-22 22:45 ` Junio C Hamano
2020-01-22 23:53 ` SZEDER Gábor
2020-01-23 6:06 ` Junio C Hamano
2020-01-23 12:11 ` yz/p4-py3, was " Johannes Schindelin
2020-01-23 18:27 ` Yang Zhao
2020-01-27 12:55 ` SZEDER Gábor
2020-01-23 14:16 ` SZEDER Gábor
2020-01-23 17:56 ` SZEDER Gábor
2020-01-23 20:52 ` Junio C Hamano
2020-01-24 17:45 ` Yang Zhao
2020-01-25 0:13 ` Johannes Schindelin [this message]
2020-01-25 8:31 ` SZEDER Gábor
2020-01-26 9:21 ` Johannes Schindelin
2020-01-23 21:39 ` Johannes Schindelin
2020-01-24 12:02 ` SZEDER Gábor
2020-01-25 0:35 ` Johannes Schindelin
2020-02-05 21:01 ` Junio C Hamano
2020-02-06 0:27 ` SZEDER Gábor
2020-02-06 8:57 ` Johannes Schindelin
2020-02-06 9:06 ` SZEDER Gábor
2020-02-06 11:45 ` Johannes Schindelin
2020-01-23 11:56 ` Johannes Schindelin
2020-01-23 4:29 ` Denton Liu
2020-01-23 6:08 ` Junio C Hamano
2020-01-23 16:54 ` Christian Couder
2020-01-23 20:23 ` Junio C Hamano
2020-01-26 20:07 ` Denton Liu
2020-01-27 18:29 ` Junio C Hamano
2020-01-27 20:26 ` [PATCH] .mailmap: fix erroneous authorship for Derrick Stolee Denton Liu
2020-01-28 17:56 ` Junio C Hamano
2020-01-29 8:59 ` What's cooking in git.git (Jan 2020, #04; Wed, 22) Denton Liu
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=nycvar.QRO.7.76.6.2001250112171.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).