From: Anton Mladenov <anton.g.mladenov@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Wrong Version On The Website ?
Date: Wed, 25 Mar 2020 10:53:57 +0100 [thread overview]
Message-ID: <701EAC93-99E2-4D7E-A991-857A7CB82E6C@gmail.com> (raw)
In-Reply-To: <20200325053455.GB651138@coredump.intra.peff.net>
Hi all,
@Brian - thanks for your quick email. I will use Homebrew this time.
@Jeff - thanks for your attention.
Stay home, stay safe!
Cheers!
> On 25 Mar 2020, at 06:34, Jeff King <peff@peff.net> wrote:
>
> On Wed, Mar 25, 2020 at 12:12:58AM +0000, brian m. carlson wrote:
>
>> The Mac and Windows builds linked to from the website are provided by
>> third parties. The Git project itself only provides source releases.
>> While the Windows builds are usually released around the same time as
>> the main source releases, the Mac builds sometimes take longer, since
>> they're done by a volunteer.
>>
>> If you're interested in the latest release, I recommend trying Homebrew,
>> as they tend to be a little more up to date.
>
> I think the web page could do a much better job of making this clear:
>
> - mentioning homebrew and possibly other sources on the /download/mac
> page
>
> - make it clear that the binary builds are provided by a 3rd party;
> they may lag official releases (and are not themselves official; I've
> never heard any complaints about them differing in behavior from what
> Git devs would expect, but I don't think anybody from this list is
> really actively paying attention to them either).
>
> Patches welcome (we take PRs at https://github.com/git/git-scm.com).
>
> -Peff
prev parent reply other threads:[~2020-03-25 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 19:20 Wrong Version On The Website ? Anton Mladenov
2020-03-25 0:12 ` brian m. carlson
2020-03-25 5:34 ` Jeff King
2020-03-25 9:53 ` Anton Mladenov [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=701EAC93-99E2-4D7E-A991-857A7CB82E6C@gmail.com \
--to=anton.g.mladenov@gmail.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).