latest git version no longer detected by base ==> and it is a pain to use
Herby G
herby.gillot at gmail.com
Sat Apr 16 19:01:07 UTC 2022
I believe the *safe.directory *config option is what we'll want to
configure to alleviate this:
https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory
On Sat, Apr 16, 2022 at 2:02 PM Ken Cunningham <
ken.cunningham.webuse at gmail.com> wrote:
> the new git is causing headaches for me too.
>
> It delivers errors based on the ownership of directories above it, to
> address this:
>
> https://github.blog/2022-04-12-git-security-vulnerability-announced/
>
> which means that any kind of git work in the macports trees (owned by
> macports) even as root now causes errors unless folder by folder exceptions
> are made. Yuk.
>
> I rolled back to the last git before this fix for the time being.
>
> Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20220416/599b34cc/attachment.htm>
More information about the macports-dev
mailing list