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

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 15, 2021, 20:50 UTC
Message-ID: <xmqqh7k7p90p.fsf@gitster.g>
In-Reply-To: <CAPyFy2Bf8t_2HggKG7LMY4u=9qBJ0-+xcx-gCv_kh7KYHg1-hw@mail.gmail.com>

Ed Maste <emaste@freebsd.org> writes:

Show 7 quoted lines

> 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?

I do not think that README, which is end-user facing, is a good place for that.

If anything, I am inclined to say that developer facing documents like SubmittingPatches and CodingGuidelines may be a better place to say that things are expected to work on X, Y and Z platforms, but I would think it is perfectly OK to start with a new feature that works only on, say, macOS, and leave it unimplemented for other platforms until somebody who is motivated enough to help fills the gap. So in that sense, "things are expected to work on these platforms" may be already stronger than what we want to say.