From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff Hostetler" <git@jeffhostetler.com>,
"Victoria Dye" <vdye@github.com>
Cc: "Jeff Hostetler via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Stefan Sundin" <git@stefansundin.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"René Scharfe" <l.s.r@web.de>,
"Jeff Hostetler" <jeffhostetler@github.com>,
"Eric DeCosta" <edecosta@mathworks.com>
Subject: Re: [PATCH] fsmonitor: eliminate call to deprecated FSEventStream function
Date: Mon, 05 Dec 2022 09:58:47 +0900 [thread overview]
Message-ID: <xmqqv8mqsm2g.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1qphuwj6.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 03 Dec 2022 10:05:17 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> I'd still prefer that our commit messages keep records of the fact
> that we stopped supporting certain older systems and what kind of
> due dilligence we did to decide it is a safe thing to do, which all
> already happened in this thread, thanks to you three discussing the
> issue. I would be happier even with "Anything older than 2014 does
> not matter to Apple, and we follow that stance" than without any ;-)
I'd propose to have an extra paragraph at the end of the commit log
message.
1: 02a55477b6 ! 1: df739b6087 fsmonitor: eliminate call to deprecated FSEventStream function
@@ Commit message
maintains the original blocking model by waiting on a mutex/condition
variable pair while the hidden thread does all of the work.
+ While the deprecated API used by the original were introduced in
+ macOS 10.5 (Oct 2007), the API used by the updated code were
+ introduced back in macOS 10.6 (Aug 2009) and has been available
+ since then. So this change _could_ break those who have happily
+ been using 10.5 (if there were such people), but these two dates
+ both predate the oldest versions of macOS Apple seems to support
+ anyway, so we should be safe.
+
Signed-off-by: Jeff Hostetler <jeffhostetler@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
next prev parent reply other threads:[~2022-12-05 0:58 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 [this message]
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
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=xmqqv8mqsm2g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=edecosta@mathworks.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).