From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Sibi Siddharthan <sibisiv.siddharthan@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2020, #01; Mon, 3)
Date: Wed, 12 Aug 2020 12:53:39 -0700 [thread overview]
Message-ID: <xmqqlfij63p8.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200812160653.GA42443@coredump.intra.peff.net> (Jeff King's message of "Wed, 12 Aug 2020 12:06:53 -0400")
Jeff King <peff@peff.net> writes:
> Yeah, I know. My main beef was that because it fails CI, the urgency of
> doing that fix gets pushed onto people working on their individual
> topics (in fact there is nothing for you to fix yet because I haven't
> even sent these topics upstream). I don't know how to solve that without
> stopping its use in the vsbuild CI job, though.
What I am not getting is in what way it blocks you (or others who do
not deeply care about Windows) to leave vsbuild CI job broken. Do
you have some automation that is gated by all the CI jobs to pass,
or do you just dislike failing CI jobs out of principle?
I pretty much got used to seeing occasional failures and learned to
ignore it (e.g. https://travis-ci.org/github/git/git/jobs/716661598
that ends with
Makefile:2467: *** unterminated variable reference. Stop.
make: *** Waiting for unfinished jobs....
).
next prev parent reply other threads:[~2020-08-12 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 5:35 What's cooking in git.git (Aug 2020, #01; Mon, 3) Junio C Hamano
2020-08-04 18:50 ` Jeff King
2020-08-04 18:58 ` Junio C Hamano
2020-08-04 19:20 ` Jeff King
2020-08-12 13:35 ` Johannes Schindelin
2020-08-12 14:19 ` Jeff King
2020-08-12 15:56 ` Sibi Siddharthan
2020-08-12 16:06 ` Jeff King
2020-08-12 19:53 ` Junio C Hamano [this message]
2020-08-12 20:11 ` Jeff King
2020-08-14 12:08 ` Johannes Schindelin
2020-08-14 12:40 ` Jeff King
2020-08-17 4:41 ` Johannes Schindelin
2020-08-17 17:19 ` Junio C Hamano
2020-08-06 3:25 ` Jiang Xin
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=xmqqlfij63p8.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sibisiv.siddharthan@gmail.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).