From: Junio C Hamano <gitster@pobox.com>
To: "Jeff Hostetler via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Stefan Sundin" <git@stefansundin.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"René Scharfe" <l.s.r@web.de>, "Victoria Dye" <vdye@github.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff Hostetler" <git@jeffhostetler.com>,
"Jeff Hostetler" <jeffhostetler@github.com>
Subject: Re: [PATCH v2] fsmonitor: eliminate call to deprecated FSEventStream function
Date: Thu, 15 Dec 2022 09:09:05 +0900 [thread overview]
Message-ID: <xmqqtu1xttni.fsf@gitster.g> (raw)
In-Reply-To: <pull.1436.v2.git.1671045153981.gitgitgadget@gmail.com> (Jeff Hostetler via GitGitGadget's message of "Wed, 14 Dec 2022 19:12:33 +0000")
"Jeff Hostetler via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Jeff Hostetler <jeffhostetler@github.com>
>
> Replace the call to `FSEventStreamScheduleWithRunLoop()` function with
> the suggested `FSEventStreamSetDispatchQueue()` function.
>
> The MacOS version of the builtin FSMonitor feature uses the
> `FSEventStreamScheduleWithRunLoop()` function to drive the event loop
> and process FSEvents from the system. This routine has now been
> deprecated by Apple. The MacOS 13 (Ventura) compiler tool chain now
> generates a warning when compiling calls to this function. In
> DEVELOPER=1 mode, this now causes a compile error.
Thanks, will requeue.
prev parent reply other threads:[~2022-12-15 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:24 [PATCH] fsmonitor: eliminate call to deprecated FSEventStream function Jeff Hostetler via GitGitGadget
2022-12-02 17:42 ` Victoria Dye
2022-12-02 18:02 ` Ævar Arnfjörð Bjarmason
2022-12-02 18:37 ` Jeff Hostetler
2022-12-02 19:08 ` Ævar Arnfjörð Bjarmason
2022-12-02 19:51 ` Victoria Dye
2022-12-02 20:34 ` Ævar Arnfjörð Bjarmason
2022-12-02 21:17 ` Victoria Dye
2022-12-02 21:44 ` Stefan Sundin
2022-12-02 23:02 ` Ævar Arnfjörð Bjarmason
2022-12-03 1:05 ` Junio C Hamano
2022-12-05 0:58 ` Junio C Hamano
2022-12-05 14:34 ` Jeff Hostetler
2022-12-05 23:13 ` Junio C Hamano
2022-12-06 17:25 ` Jeff Hostetler
2022-12-14 19:12 ` [PATCH v2] " Jeff Hostetler via GitGitGadget
2022-12-15 0:09 ` Junio C Hamano [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=xmqqtu1xttni.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@stefansundin.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jeffhostetler@github.com \
--cc=l.s.r@web.de \
--cc=vdye@github.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).