git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
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?

  reply	other threads:[~2021-04-15 20:38 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 22:03 [PATCH] hooks: propose repository owner " Albert Cui via GitGitGadget
2021-03-18 22:29 ` Junio C Hamano
2021-03-18 23:45   ` Albert Cui
2021-03-19  1:28 ` brian m. carlson
2021-03-19 10:27 ` Ævar Arnfjörð Bjarmason
2021-04-06  0:35   ` Albert Cui
2021-04-07 22:47     ` Ævar Arnfjörð Bjarmason
2021-06-21 19:36       ` Jonathan Tan
2021-06-21 20:35         ` Ævar Arnfjörð Bjarmason
2021-03-26  1:43 ` [PATCH v2] hooks: propose project " Albert Cui via GitGitGadget
2021-03-29 23:20   ` Emily Shaffer
2021-04-01 20:02     ` Albert Cui
2021-03-30 15:24   ` Derrick Stolee
2021-04-05 22:45     ` Albert Cui
2021-04-05 23:09       ` Junio C Hamano
2021-04-05 23:40         ` Albert Cui
2021-04-06  0:13           ` Junio C Hamano
2021-04-06  0:27             ` Albert Cui
2021-04-06 23:15       ` brian m. carlson
2021-04-07  7:53         ` Ævar Arnfjörð Bjarmason
2021-04-07 13:09           ` Derrick Stolee
2021-04-07 18:40             ` Albert Cui
2021-04-07 20:02               ` Junio C Hamano
2021-04-07 22:23                 ` Ævar Arnfjörð Bjarmason
2021-04-15 16:52             ` Ed Maste
2021-04-15 19:41               ` Junio C Hamano
2021-04-15 20:37                 ` Ed Maste [this message]
2021-04-15 20:50                   ` Junio C Hamano
2021-04-15 22:28                   ` brian m. carlson
2021-04-02  9:59   ` Ævar Arnfjörð Bjarmason
2021-04-05 23:42     ` Albert Cui
2021-04-02 10:30   ` Ævar Arnfjörð Bjarmason
2021-04-03  0:58     ` Albert Cui
2021-04-24  1:38   ` [PATCH v3] " Albert Cui via GitGitGadget
2021-04-28  2:48     ` Junio C Hamano
2021-05-05 19:11     ` [PATCH v4] " Albert Cui via GitGitGadget
2021-06-03  3:31       ` Jonathan Tan
2021-06-03 20:16         ` Albert Cui
2021-06-03 22:10           ` Jonathan Tan

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPyFy2Bf8t_2HggKG7LMY4u=9qBJ0-+xcx-gCv_kh7KYHg1-hw@mail.gmail.com' \
    --to=emaste@freebsd.org \
    --cc=albertqcui@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=stolee@gmail.com \
    --subject='Re: [PATCH v2] hooks: propose project configured hooks' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).