From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
Taylor Blau <me@ttaylorr.com>,
Dragan Simic <dsimic@manjaro.org>,
Git List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Defining a platform support policy
Date: Mon, 22 Jan 2024 16:31:14 -0800 [thread overview]
Message-ID: <xmqqil3kriul.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZnHGTFhfR6e6r=GMSfVbSNgLoHF-opaWYLbHppiuzi+Rg@mail.gmail.com> (Emily Shaffer's message of "Mon, 22 Jan 2024 15:17:50 -0800")
Emily Shaffer <nasamuffin@google.com> writes:
> But, Randall's remarks bring up something pretty compelling: I don't
> think Git has a clearly defined platform support policy. As far as I
> can tell, the support policy now is "if you run `make test` on it and
> breaks, and you let us know, we'll try to fix it"
I doubt this part. If there is somebody motivated enough among us
who has access to such a platform, then that person may try to fix
it and if the fix is not too ugly, I may accept such a patch as the
upstream maintainer. So your "you let us know we'll try" does not
reflect reality at all. The major platforms luckily have such
motivated somebody almost always available for them. Niche ones,
perhaps not.
> ..., but nowhere do I see "how to know if your platform is
> supported" or even "here are platforms we have heard Git works OK on".
Yup. Patches, with commitments to keep such lists up-to-date, are
very much welcome.
Thanks.
next prev parent reply other threads:[~2024-01-23 0:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:16 [DISCUSS] Introducing Rust into the Git project Taylor Blau
2024-01-10 21:57 ` Dragan Simic
2024-01-10 22:11 ` Junio C Hamano
2024-01-10 22:15 ` rsbecker
2024-01-10 22:26 ` Taylor Blau
2024-01-10 23:52 ` rsbecker
2024-01-11 0:59 ` Elijah Newren
2024-01-11 1:44 ` rsbecker
2024-01-11 2:21 ` Elijah Newren
2024-01-11 2:57 ` rsbecker
2024-01-11 5:06 ` Elijah Newren
2024-01-11 6:56 ` Patrick Steinhardt
2024-01-11 13:07 ` rsbecker
2024-01-11 2:55 ` brian m. carlson
2024-01-11 3:24 ` rsbecker
2024-01-11 20:07 ` Trevor Gross
2024-01-11 21:28 ` rsbecker
2024-01-11 23:23 ` Trevor Gross
2024-01-22 23:17 ` Defining a platform support policy (Was: [DISCUSS] Introducing Rust into the Git project) Emily Shaffer
2024-01-23 0:11 ` rsbecker
2024-01-23 0:57 ` Defining a platform support policy Junio C Hamano
2024-01-23 0:31 ` Junio C Hamano [this message]
2024-01-24 7:54 ` Defining a platform support policy (Was: [DISCUSS] Introducing Rust into the Git project) Elijah Newren
2024-01-10 23:40 ` [DISCUSS] Introducing Rust into the Git project brian m. carlson
2024-01-11 0:33 ` Elijah Newren
2024-01-11 5:39 ` Dragan Simic
2024-01-11 16:57 ` Elijah Newren
2024-01-17 21:30 ` Dragan Simic
2024-01-24 4:15 ` Elijah Newren
2024-01-24 5:14 ` Dragan Simic
2024-01-11 0:12 ` Elijah Newren
2024-01-11 5:33 ` Dragan Simic
2024-01-11 1:56 ` brian m. carlson
2024-01-11 11:45 ` Sam James
2024-01-11 23:48 ` brian m. carlson
2024-01-12 8:24 ` Sam James
2024-01-12 14:46 ` Antoni Boucher
2024-01-11 23:53 ` Trevor Gross
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=xmqqil3kriul.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=nasamuffin@google.com \
--cc=rsbecker@nexbridge.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 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).