From: Junio C Hamano <gitster@pobox.com>
To: Collin Funk <collin.funk1@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: [PATCH] CodingGuidelines: document test balloons in flight
Date: Sat, 26 Jul 2025 16:15:21 -0700 [thread overview]
Message-ID: <xmqqcy9m1r3q.fsf@gitster.g> (raw)
In-Reply-To: <m1seily1e3.fsf@gmail.com> (Collin Funk's message of "Thu, 24 Jul 2025 09:55:16 -0700")
Collin Funk <collin.funk1@gmail.com> writes:
>> So the only effect it would have is to smoke out truly slow platform
>> maintainers; if their users are happy enough with such slow upgrade,
>> they have lived and they can live with versions of Git that are
>> years stale that we no longer care about.
>
>
> For what it is worth, Gnulib and threfore Coreutils, among others, began
> using compound literals in 2017 and it seems to have not caused any
> problems [1]. Even 'pcc' supports them.
Thanks. Our worry however includes platforms outside the Open
Source and/or Free Software ecosystem, which would not be helped
very much.
next prev parent reply other threads:[~2025-07-26 23:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:27 [PATCH] strbuf: add compound literal test balloon Phillip Wood
2025-07-14 14:26 ` Junio C Hamano
2025-07-15 8:53 ` Patrick Steinhardt
2025-07-15 9:44 ` Phillip Wood
2025-07-15 16:24 ` Junio C Hamano
2025-07-16 14:29 ` Phillip Wood
2025-07-23 18:01 ` Junio C Hamano
2025-07-23 19:31 ` [PATCH] CodingGuidelines: document test balloons in flight Junio C Hamano
2025-07-24 6:55 ` Patrick Steinhardt
2025-07-24 16:39 ` Junio C Hamano
2025-07-24 16:55 ` Collin Funk
2025-07-26 23:15 ` Junio C Hamano [this message]
2025-07-24 14:26 ` Phillip Wood
2025-07-24 16:23 ` Junio C Hamano
2025-07-16 14:32 ` [PATCH] strbuf: add compound literal test balloon Phillip Wood
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=xmqqcy9m1r3q.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=collin.funk1@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
/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).