From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Victoria Dye via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, philipoakley@iee.email,
eschwartz@archlinux.org, "Carlo Arenas" <carenas@gmail.com>,
"Jeff King" <peff@peff.net>, "Victoria Dye" <vdye@github.com>
Subject: Re: [PATCH v2] async_die_is_recursing: work around GCC v11.x issue on Fedora
Date: Thu, 04 Nov 2021 10:46:24 -0700 [thread overview]
Message-ID: <xmqqcznf3jbj.fsf@gitster.g> (raw)
In-Reply-To: <29114bd7-1c81-7580-c8c0-88904dd013db@gmail.com> (Derrick Stolee's message of "Thu, 4 Nov 2021 09:08:00 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> Having our CI go red because the 'latest' feed changed something is
> probably the best "feed" to subscribe to, since we only get notified
> if it matters.
>
> Better to have automation go red than for us to not realize our code
> doesn't work on newer platforms because our CI hasn't been updated.
I consider this a better implementation of what Æver suggested ;-)
And an incident like this is one of the reasons why I like the "CI
does not stop after seeing the first problem" behaviour. In a short
term, people can ignore a particular known failure and ensure they
do not introduce any new ones.
Thanks.
next prev parent reply other threads:[~2021-11-04 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 1:47 [PATCH] async_die_is_recursing: fix use of pthread_getspecific for Fedora Victoria Dye via GitGitGadget
2021-11-04 2:23 ` Carlo Arenas
2021-11-04 2:37 ` Jeff King
2021-11-04 3:20 ` Carlo Arenas
2021-11-04 5:56 ` Jeff King
2021-11-04 4:01 ` [PATCH v2] async_die_is_recursing: work around GCC v11.x issue on Fedora Victoria Dye via GitGitGadget
2021-11-04 5:58 ` Jeff King
2021-11-04 6:35 ` Junio C Hamano
2021-11-04 9:42 ` Ævar Arnfjörð Bjarmason
2021-11-04 13:08 ` Derrick Stolee
2021-11-04 17:46 ` Junio C Hamano [this message]
2021-11-05 21:45 ` Junio C Hamano
2021-11-04 8:43 ` Johannes Schindelin
2021-11-04 9:46 ` Carlo Arenas
2021-11-04 16:33 ` Johannes Schindelin
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=xmqqcznf3jbj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--cc=philipoakley@iee.email \
--cc=stolee@gmail.com \
--cc=vdye@github.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.