From: Junio C Hamano <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: Git List <email@example.com>, Eric Sunshine <firstname.lastname@example.org> Subject: Re: [PATCH v2] CodingGuidelines: explicitly allow "local" for test scripts Date: Tue, 04 May 2021 12:01:38 +0900 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (=?utf-8?B?IsOGdmFyIEFy?= =?utf-8?B?bmZqw7Zyw7A=?= Bjarmason"'s message of "Mon, 03 May 2021 11:01:27 +0200") Ævar Arnfjörð Bjarmason <email@example.com> writes: > Is there any portability reason to avoid "local" in the porcelains? I > don't have any plans for using it, but I don't see why we'd explicitly > forbid it. Things that are not even in POSIX are forbidden unless explicitly allowed. In general, he way we encouraged people to think has been "don't use it, it is not even in POSIX" and "even if it is in POSIX, we know the support by platform/implementation X is broken, so let's not use it". It has been successfully helped us to stay out of portability troubles. There may be a few tiny cases where we said "practically everybody we care about has it, even though it is not in POSIX, and it makes our life so vastly be better" to explicitly allow some feature, though. And "local"? Not absolutely essential, unless you are doing a library that you want to avoid stepping on users' toes. Besides, we are no longer adding scripted Porcelains left and right---rather, people are actively rewriting them. Thanks.
next prev parent reply other threads:[~2021-05-04 3:01 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 4:10 [PATCH] " 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 [this message] 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 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
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2] CodingGuidelines: explicitly allow "local" for test scripts' \ /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
Code repositories for project(s) associated with this 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).