From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: bc/require-c99 + jc/c99-var-decl-in-for-loop
Date: Sun, 28 Nov 2021 18:29:47 -0800 [thread overview]
Message-ID: <xmqqh7bv4rtw.fsf@gitster.g> (raw)
In-Reply-To: 211126.86czmnhwu4.gmgdl@evledraar.gmail.com
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> On Wed, Nov 24 2021, Junio C Hamano wrote:
>
>> * bc/require-c99 (2021-11-18) 1 commit
>> . git-compat-util: add a test balloon for C99 support
>>
>> Weather balloon to break people with compilers that do not support
>> C99.
>
> It would be nice if they'd upgrade, but maybe breaking those people is
> going a bit far :)
You cannot tell who if anybody is not ready without a small piece of
change, which is very easy to revert locally, that would break them
hard. If you look at the patch in question, especially if you pay
attention to what message it gives those who are not ready when it
happens, I would think you agree with the patch thta it is not going
too far.
next prev parent reply other threads:[~2021-11-29 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 5:56 What's cooking in git.git (Nov 2021, #06; Wed, 24) Junio C Hamano
2021-11-25 13:11 ` Philip Oakley
2021-11-26 13:11 ` bc/require-c99 + jc/c99-var-decl-in-for-loop (was: What's cooking in git.git (Nov 2021, #06; Wed, 24)) Ævar Arnfjörð Bjarmason
2021-11-29 2:29 ` Junio C Hamano [this message]
2021-11-29 15:56 ` vd/sparse-reset (Was: " Victoria Dye
2021-11-29 20:48 ` vd/sparse-reset Junio C Hamano
2021-11-29 22:30 ` Submodules UX overhaul update (was: What's cooking in git.git (Nov 2021, #06; Wed, 24)) Emily Shaffer
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=xmqqh7bv4rtw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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.