git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: git@vger.kernel.org, "Randall S. Becker" <rsbecker@nexbridge.com>,
	"Taylor Blau" <me@ttaylorr.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2] Documentation: add platform support policy
Date: Mon, 15 Jul 2024 16:46:40 -0700	[thread overview]
Message-ID: <xmqq34oa1an3.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZnUbgX1MpisdS+TkGLFrBUyX_x_M_Q6iZ2n_AhP8r4mNA@mail.gmail.com> (Emily Shaffer's message of "Mon, 15 Jul 2024 15:20:51 -0700")

Emily Shaffer <nasamuffin@google.com> writes:

> If I fudge with the rewrite a little, I get:
>
> """
> Git has a history of providing broad "support" for exotic platforms
> and older
> platforms, without an explicit commitment. Stakeholders of these platforms may
> want a more predictable support commitment. This is only possible when platform
> stakeholders supply Git developers with adequate tooling, so we can
> test for
> compatibility or develop workarounds for platform-specific quirks on
> our own.
> Various levels of tooling will allow us to make more solid commitments around
> Git's compatibility with your platform.
> """

This reads well.

> """
> Note that this document is about maintaining existing support for a platform
> that has generally worked in the past; for adding support to a
> platform which
> doesn't generally work with Git, the stakeholders for that platform are expected
> to do the bulk of that work themselves. We will consider such patches
> if they
> don't make life harder for other supported platforms, and you may well find a
> contributor interested in working on that support, but the Git
> community as a
> whole doesn't feel an obligation to perform such work.
> """

The part before "We will consider" reads very well.  The part after
that, I haven't formed a firm opinion on (yet).

> """
> * You should run nightly tests against the `next` branch and publish breakage
>   reports to the mailing list immediately when they happen.
>
> ** You may want to ask to join the
>    mailto:git-security@googlegroups.com[security
>    mailing list] in order to run tests against the fixes proposed there, too.
> """

Looking good, I guess.

THanks.

  reply	other threads:[~2024-07-15 23:46 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 22:50 [PATCH] Documentation: add platform support policy Emily Shaffer
2024-07-09 23:16 ` brian m. carlson
2024-07-11 18:14   ` Emily Shaffer
2024-07-11 20:12     ` Kyle Lippincott
2024-07-11 20:24       ` rsbecker
2024-07-11 20:57       ` Emily Shaffer
2024-07-11 22:24     ` brian m. carlson
2024-07-11 23:15       ` Emily Shaffer
2024-07-12 19:33         ` brian m. carlson
2024-07-12 19:46           ` rsbecker
2024-07-15 22:28             ` Emily Shaffer
2024-07-15 22:50               ` rsbecker
2024-07-15 22:23           ` Emily Shaffer
2024-07-10  0:57 ` Junio C Hamano
2024-07-10 18:55   ` Emily Shaffer
2024-07-10 20:13     ` Junio C Hamano
2024-07-11 18:26       ` Emily Shaffer
2024-07-10 20:20     ` rsbecker
2024-07-11 18:19       ` Emily Shaffer
2024-07-11 18:53         ` rsbecker
2024-07-10 19:11 ` Kyle Lippincott
2024-07-11 18:37   ` Emily Shaffer
2024-07-11 19:36     ` Junio C Hamano
2024-07-11 19:55       ` Junio C Hamano
2024-07-11 20:25     ` Kyle Lippincott
2024-07-11 23:24 ` [PATCH v2] " Emily Shaffer
2024-07-12 18:15   ` Junio C Hamano
2024-07-15 22:20     ` Emily Shaffer
2024-07-15 23:46       ` Junio C Hamano [this message]
2024-07-16 17:58         ` Emily Shaffer
2024-07-16 18:20           ` rsbecker
2024-07-17 18:16           ` Junio C Hamano
2024-07-18 17:38   ` [PATCH v3] " Emily Shaffer
2024-07-18 18:22     ` Emily Shaffer
2024-07-18 21:47       ` Junio C Hamano
2024-07-18 22:46     ` Junio C Hamano
2024-07-18 23:45       ` rsbecker
2024-07-25 16:53         ` Emily Shaffer
2024-07-25 18:52       ` Emily Shaffer
2024-07-25 19:34         ` Junio C Hamano
2024-07-25 19:40         ` rsbecker
2024-07-23  9:02     ` Patrick Steinhardt
2024-07-25 20:27       ` Emily Shaffer
2024-07-23 21:49     ` Josh Steadmon
2024-07-25 20:31       ` Emily Shaffer
2024-07-30 17:54     ` [PATCH v4] " Emily Shaffer
2024-07-30 19:26       ` Junio C Hamano
2024-07-30 20:41         ` Emily Shaffer
2024-07-30 21:24           ` Junio C Hamano
2024-07-30 22:40             ` rsbecker
2024-07-31 17:20               ` Emily Shaffer
2024-07-31 20:58                 ` rsbecker
2024-08-02 22:19       ` [PATCH v5] " Emily Shaffer
2024-08-02 23:31         ` Junio C Hamano
2024-08-02 23:32           ` rsbecker

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=xmqq34oa1an3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --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).