All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Joachim Schmitz <jojo@schmitz-digital.de>,
	Matt Kraai <kraai@ftbfs.org>,
	"Randall S. Becker" <randall.becker@nexbridge.ca>,
	git@vger.kernel.org, Aleksey Kliger <alklig@microsoft.com>
Subject: Re: [PATCH] config.mak.uname: enable OPEN_RETURNS_EINTR for macOS Big Sur
Date: Wed, 03 Mar 2021 16:47:20 -0800	[thread overview]
Message-ID: <xmqqv9a7g2xz.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YD+SCtzmtWgFArwW@coredump.intra.peff.net> (Jeff King's message of "Wed, 3 Mar 2021 08:41:30 -0500")

Jeff King <peff@peff.net> writes:

> Thanks. I guess we're a bit late to make it into the upcoming release.
> Certainly we have survived for many years without this particular
> bugfix, so in that sense it is not urgent. But I do wonder if we will
> see more reports as more people start using the new macOS release. So it
> might be good to keep in mind for maint, if we cut a minor release.
>
> Or alternatively, we could include _just_ the first patch. That's low
> risk, since you have to enable to knob yourself, but it gives people an
> option if they run into the symptom. But even that is probably not that
> urgent. People can also cherry-pick the patch, after all (and a
> distributor like homebrew can probably include the patch in their recipe
> if need be).

True.  The topic is forked at somewhere mergeable to 'maint' so
distro folks who are interested can merge them down later.  I think
it is small and safe enough to merge them both down to the upcoming
release, though.


  reply	other threads:[~2021-03-04  1:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  4:43 [PATCH] wrapper: add workaround for open() returning EINTR Jeff King
2021-02-24  4:46 ` Jeff King
2021-02-24  5:36   ` Junio C Hamano
2021-02-24 18:20     ` Jeff King
2021-02-26  6:14       ` [PATCH v2] Makefile: add OPEN_RETURNS_EINTR knob Jeff King
2021-02-26 22:17         ` Junio C Hamano
2021-03-01  9:29           ` [PATCH] config.mak.uname: enable OPEN_RETURNS_EINTR for macOS Big Sur Jeff King
2021-03-01 17:17             ` Junio C Hamano
2021-03-01 23:57             ` Junio C Hamano
2021-03-03 13:41               ` Jeff King
2021-03-04  0:47                 ` Junio C Hamano [this message]
2021-02-24  4:50 ` [PATCH] wrapper: add workaround for open() returning EINTR Taylor Blau
2021-02-24  7:20 ` Johannes Sixt
2021-02-24 18:23   ` Jeff King
2021-02-26  6:17     ` Jeff King

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=xmqqv9a7g2xz.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=alklig@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=jojo@schmitz-digital.de \
    --cc=kraai@ftbfs.org \
    --cc=peff@peff.net \
    --cc=randall.becker@nexbridge.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.