From: Jeff King <peff@peff.net>
To: M Hickford <mirth.hickford@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Which macOS versions does Git support?
Date: Fri, 19 May 2023 05:09:17 -0400 [thread overview]
Message-ID: <20230519090917.GB3515410@coredump.intra.peff.net> (raw)
In-Reply-To: <CAGJzqsnS3SnoW__aPQ+13s+-b3a+makCjWxR=z6mjgBBnuKjLg@mail.gmail.com>
On Fri, May 19, 2023 at 08:00:00AM +0100, M Hickford wrote:
> Hi. Does anyone know which macOS versions are supported by Git?
I don't think we have any formal decision here (or for any other
platform; it is usually a cost/benefit for individual features we may
want to depend on).
> Motivation: I spotted that git-credential-osxkeychain.c uses a
> deprecated API. SecKeychainAddInternetPassword was deprecated in
> 2014's macOS 10.10 [1]. Replacement SecItemAdd was introduced in
> 2009's macOS 10.6 [2].
+cc Taylor, who I know was looking into this recently.
I'd guess that anything older than 2009 is probably not worth worrying
about.
> Further motivation: If I understand the documentation correctly, the
> new SecItemAdd API has better support for storing attributes alongside
> secrets, which might be handy for storing Git credential's new
> password_expiry_utc attribute (d208bfd, credential: new attribute
> password_expiry_utc, 2023-02-18).
Yeah, that would be a nice bonus (in addition to avoiding a deprecated
interface).
-Peff
next prev parent reply other threads:[~2023-05-19 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 7:00 Which macOS versions does Git support? M Hickford
2023-05-19 9:09 ` Jeff King [this message]
2023-05-19 17:49 ` Jeff Hostetler
2023-05-20 0:37 ` Carlo Marcelo Arenas Belón
2023-05-20 7:36 ` M Hickford
2023-05-22 19:24 ` 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=20230519090917.GB3515410@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=mirth.hickford@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 read-only IMAP folder(s) and NNTP newsgroup(s).