From: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>
Cc: Git List <firstname.lastname@example.org>,
Eric Sunshine <email@example.com>,
"brian m. carlson" <firstname.lastname@example.org>
Subject: Re: [PATCH v2] CodingGuidelines: explicitly allow "local" for test scripts
Date: Tue, 04 May 2021 17:09:54 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Tue, May 04 2021, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> writes:
>> It's effectively synonymous with saying "we still want to support git on
>> platforms that are so broken they can't even run a single test in our
>> test suite".
> Not really. Those on such a platform would (rightly) say that it is
> the test suite that is broken and out of compliance.
Indeed. But the lack of any reports about that suggests that in practice
this is universally supported enough to be a hard dependency.
In any case, it's clear you don't agree and you manage the patch
queue. So I'll leave it at that.
My aim here was to discover if we had any reason to think that "local"
was less universally implemented than other POSIX/C89-plus features we
rely on. It seems that it's not.
next prev parent reply other threads:[~2021-05-04 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 4:10 [PATCH] CodingGuidelines: explicitly allow "local" for test scripts Junio C Hamano
2021-05-03 4:21 ` Eric Sunshine
2021-05-03 5:21 ` Junio C Hamano
2021-05-03 5:23 ` [PATCH v2] " Junio C Hamano
2021-05-03 9:01 ` Ævar Arnfjörð Bjarmason
2021-05-04 3:01 ` Junio C Hamano
2021-05-04 12:27 ` Ævar Arnfjörð Bjarmason
2021-05-04 12:50 ` Junio C Hamano
2021-05-04 15:09 ` Ævar Arnfjörð Bjarmason [this message]
2021-05-04 20:22 ` Felipe Contreras
2021-05-04 23:17 ` brian m. carlson
2021-05-04 23:55 ` Junio C Hamano
2021-05-05 0:08 ` Felipe Contreras
2021-05-05 1:58 ` brian m. carlson
2021-05-05 3:59 ` Felipe Contreras
2021-05-05 14:16 ` Jeff King
2021-05-05 17:18 ` Felipe Contreras
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:
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 \
* 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
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).