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

[Junio C Hamano <gitster@pobox.com>]

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 [*].

The best you can get out of here is: if you find portability issues
when you tried to make it work on your favorite platform, you can
raise it here and (1) somebody with more Git experience on the same
platform may solve it for you, (2) somebody with similar Git
experience as you do (or less) on the same platform may solve it
with you, or (3) somebody without acess to the platform may offer to
help you solve it.  

You cannot reasonably expect more than that from us on this list.

However, major platforms have their own (often binary) packaging
system that offer Git packaged for their users.  Debian/Ubuntu ship
their own .deb, Git-for-Windows binary installer is made available
promptly after we release a new version, macOS folks have Apple Git
and homebrew or macPorts or whatever (but do not quote me on this; I
am not an Apple user).  What they do is not under our control, and
you need to ask them what their support policies, EOL timelines, and
such.  Some of these packagers lurk around here and may respond, but
that is you getting lucky ;-)


[Footnote]

* 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.