git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Michał Staruch" <msta@cinkciarz.pl>
Cc: Tim Harper <timcharper@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: Is OS X still supported?
Date: Thu, 14 Apr 2016 09:14:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1604140845370.2967@virtualbox> (raw)
In-Reply-To: <CAN1difsnc_FdDhJ+gZoR8o4VK3Xg0eyCsyqUS7DDF328B3Pjhg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

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.

> 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

      reply	other threads:[~2016-04-14  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN1difv6C9VSwy6DAz7++R6PP6hpg9MD8v1aKk_4VTdBP5RwHw@mail.gmail.com>
     [not found] ` <xmqq4mbg2eqa.fsf@gitster.mtv.corp.google.com>
     [not found]   ` <87EB5631-EB8F-41C3-B92C-3BEF03F1A9AF@gmail.com>
2016-04-05 21:08     ` Is OS X still supported? Michał Staruch
2016-04-14  7:14       ` Johannes Schindelin [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=alpine.DEB.2.20.1604140845370.2967@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=msta@cinkciarz.pl \
    --cc=timcharper@gmail.com \
    /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).