Re: Is OS X still supported?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 14, 2016, 07:14 UTC
Message-ID: <alpine.DEB.2.20.1604140845370.2967@virtualbox>
In-Reply-To: <CAN1difsnc_FdDhJ+gZoR8o4VK3Xg0eyCsyqUS7DDF328B3Pjhg@mail.gmail.com>

Hi Michał,

you probably would have received a more timely response if you

1. had avoided top-posting, and
2. had kicked into action yourself rather than feeling somebody else
   should solve your problem.

On Tue, 5 Apr 2016, Michał Staruch wrote:

> Thanks for the information that binary builds are availably on
> SourceForge faster than on git-scm. I can see the v2.8.1 for OS X was
> uploaded few hours ago to the SF, so my main problem (lack of security
> fixes in git for OS X) is solved.

You are welcome, not only for the information, of course, but also for the bug fixes. Would be nice to thank hard-working people like Peff for that, every once in a while.

Show 5 quoted lines

> The automation process should be probably reviewed, though - because all
> the other folks around the world using git-scm (not the SF) to download
> OS X builds are still stuck at v2.6.4. Ideally git-scm would point to
> the new Mac version within single minutes since the release (or even
> seconds) - not hours, days, or weeks.

The first time I read this paragraph, I closed the mail right then and there. And I normally would not have looked at it again.

You see, the code running git-scm.com is Open Source, which means that you can fix it just as well as everybody else. Of course it takes a bit more effort than to tell other people what you think they should do, yet taking action would have been the appropriate thing to do. Admittedly I find that sense of entitlement that I read in the above-quoted paragraph quite appalling.

So why did I open this mail again, then? Easy: I did not notice any other report of the same issue, and the problem was shared by one of my colleagues, so I went ahead and fixed it (note that I am probably even less of a Ruby/Rake expert than you are, yet the documentation how to develop this beast locally is so good that even I was able to develop and test the fix):

	https://github.com/git/git-scm.com/pull/741

I guess this is your lucky day ;-)

Ciao, Johannes