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 v3] Documentation: add platform support policy
Date: Thu, 25 Jul 2024 12:34:20 -0700	[thread overview]
Message-ID: <xmqqjzh9fepv.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZmKD5su=1-kw7x590zVdkqT1xPMs1VumH1j=aMHtD4mcg@mail.gmail.com> (Emily Shaffer's message of "Thu, 25 Jul 2024 11:52:50 -0700")

Emily Shaffer <nasamuffin@google.com> writes:

> It's not quite my favorite, still, because I guess that LTS distros
> could get to a point we don't want to support (do we really want to
> provide cutting-edge git features to a 25-year-old LTS distro, for
> example?). Plus, "just look at everyone else's homework and use that"
> feels a little weird.

But essentially that is what we end up doing anyway, no?  If a
platform is used heavily by some of us, they get more attention
because we would be the first to notice breakage on it.  Like it or
not, the population distribution of development community members on
different platforms would not align with the population distribution
of general public, but without access to and familiarlity with the
platform, and without motivation and time we can spend on it, none
of us would feel compelled to look into an issue that only surfaces
on an unfamiliar platform.  So it is inevitable that "you'd have
better chance of being helped by us if you make it as similar to
platforms that we are familiar with as you can" holds true.

> Will keep thinking on this, I'd welcome other suggestions for phrasing.

Likewise here.

  reply	other threads:[~2024-07-25 19:34 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
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 [this message]
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=xmqqjzh9fepv.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).