Skip to content

monitor components: monitor mingw-w64-clang#4487

Merged
rimrul merged 1 commit intogit-for-windows:mainfrom
rimrul:monitor-clang-package
Oct 19, 2023
Merged

monitor components: monitor mingw-w64-clang#4487
rimrul merged 1 commit intogit-for-windows:mainfrom
rimrul:monitor-clang-package

Conversation

@rimrul
Copy link
Member

@rimrul rimrul commented Jul 1, 2023

after merging git-for-windows/MINGW-packages#75 we'll want to be notified when Msys2 updates their mingw-w64-clang package.

after merging git-for-windows/MINGW-packages#75
we'll want to be notified when Msys2 updates their mingw-w64-clang package.

Signed-off-by: Matthias Aßhauer <[email protected]>
@rimrul rimrul force-pushed the monitor-clang-package branch from a3acb07 to 7e6c16d Compare July 1, 2023 10:48
@rimrul rimrul changed the title fixup! Add a GitHub workflow to monitor component updates monitor components: monitor mingw-w64-clang Jul 1, 2023
Copy link
Member

@dscho dscho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good thinking!

@dscho
Copy link
Member

dscho commented Jul 2, 2023

I'll leave this unmerged until we build Git for Windows' first customized mingw-w64-clang-aarch64-clang package.

@dscho
Copy link
Member

dscho commented Jul 6, 2023

@rimrul I actually want to release a v2.41.0(2) including the new major OpenSSL version and an updated Git Credential Manager (I wanted to wait for it for a bit at first, but upstream Git seems not to move toward a v2.41.1).

How about using this here PR as "an excuse" to deploy this version? (There are two more candidate PRs to use for this, which I also added to the milestone because I plan on merging them, too).

@dscho
Copy link
Member

dscho commented Jul 6, 2023

How about using this here PR as "an excuse" to deploy this version?

On further thought, it's probably best not to rush this PR, and to use #4484 to branch-deploy Git for Windows instead.

@dscho
Copy link
Member

dscho commented Jul 6, 2023

How about using this here PR as "an excuse" to deploy this version?

On further thought, it's probably best not to rush this PR, and to use #4484 to branch-deploy Git for Windows instead.

And since that PR seems to require a little bit more work, I think I'll use #4438 instead.

@rimrul rimrul merged commit 4991b61 into git-for-windows:main Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments