Re: [PATCH v2] hooks: propose project configured hooks

From: Ed Maste <emaste@freebsd.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Derrick Stolee" <stolee@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	"Albert Cui" <albertqcui@gmail.com>,
	"git mailing list" <git@vger.kernel.org>
Subject: Re: [PATCH v2] hooks: propose project configured hooks
Date: Thu, 15 Apr 2021 16:37:54 -0400	[thread overview]
Message-ID: <CAPyFy2Bf8t_2HggKG7LMY4u=9qBJ0-+xcx-gCv_kh7KYHg1-hw@mail.gmail.com> (raw)
In-Reply-To: <xmqq7dl3qqrh.fsf@gitster.g>

On Thu, 15 Apr 2021 at 15:41, Junio C Hamano <gitster@pobox.com> wrote:
>
> Ed Maste <emaste@freebsd.org> writes:
>
> > On Thu, 18 Mar 2021 at 21:29, brian m. carlson
> > <sandals@crustytoothpaste.net> wrote:
> >> > +* Works across Windows/Linux/macOS
> >>
> >> Git supports other platforms as well.
> >
> > In particular, FreeBSD is an example of a platform that is not in the
> > above list, but included in Git's CI. Is there an explicit list of
> > supported platforms (and perhaps a notion of support tiers)?
>
> It is not like there is a Git company who employs developers to
> support certain platforms.  This is the mailing list for the open
> source development community for Git, and Developers come and leave
> over time [*].

I'm sorry that my query wasn't clear; I have no expectation of Git
volunteers providing support (in the commercial sense) for any
particular platform.

What I am interested in is the Git community's expectations around
platform support, with respect to new features, changes that break one
or more platforms, and similar. I submitted portability improvements
for FreeBSD, and certainly expected that if a change introduced a
regression on one of Linux, Windows, or macOS it would not be
accepted.

> * You can peek into config.mak.uname to see the list of platforms
>   that have had a working Git some time in the past.  Hopefully most
>   of them are still up-to-date and working, but we wouldn't even
>   know if a minority platform, for which an entry for it was added
>   to the file in the past by some developer who needed a working Git
>   on it, no longer works with the latest version of Git with recent
>   toolchains after the original developer lost interest.

Yes - this is what I'm wondering about. It seems this information is
not available other than by inspecting config.mak.uname or reading
mailing list archives. I can also look at .travis.yml, .cirrus.yml,
and .github/workflows/main.yml to get a sense of the platforms
supported by Git's CI. That includes at least various versions or
flavours of Linux, macOS, Windows, and FreeBSD. Is it worth putting a
sentence or two in README.md about this?