From: Derrick Stolee <derrickstolee@github.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: criteria for linking to binaries from git-scm.com?
Date: Thu, 13 Apr 2023 09:43:07 -0400 [thread overview]
Message-ID: <bdd76013-8cb8-ceaa-7ea0-55de3e1fbad4@github.com> (raw)
In-Reply-To: <ZDdMKNJ/4njF0Jdp@tapette.crustytoothpaste.net>
On 4/12/2023 8:26 PM, brian m. carlson wrote:
> On 2023-04-12 at 08:00:19, Jeff King wrote:
>> There's an interesting question raised in an issue in the git-scm.com
>> repo that I think would benefit from input from community folks here.
>>
>> The link is:
>>
>> https://github.com/git/git-scm.com/issues/1774#issuecomment-1504829495
>>
>> but the tl;dr is:
>>
>> From a supply chain perspective, what are our criteria for linking to
>> a third party's pre-built binaries from git-scm.com?
>
> I think we should ideally suggest distribution binaries where those are
> autobuilt and the distributor is complying with the license. For macOS,
> Apple is providing their own binaries, and if people want more
> up-to-date versions, we could suggest Homebrew. For Linux and BSD
> systems, that would be pointing people to their OS distributor.
And on this note, https://git-scm.com/download/mac lists
Binary installer
Tim Harper provides an installer for Git. The latest version is
2.33.0, which was released over 1 year ago, on 2021-08-30.
Perhaps it is time to drop this reference?
Thanks,
-Stolee
prev parent reply other threads:[~2023-04-13 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 8:00 criteria for linking to binaries from git-scm.com? Jeff King
2023-04-13 0:26 ` brian m. carlson
2023-04-13 13:43 ` Derrick Stolee [this message]
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=bdd76013-8cb8-ceaa-7ea0-55de3e1fbad4@github.com \
--to=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).