Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New patch release with fix of #3189? #3335

Closed
leha-bot opened this issue Mar 6, 2023 · 1 comment
Closed

New patch release with fix of #3189? #3335

leha-bot opened this issue Mar 6, 2023 · 1 comment
Labels

Comments

@leha-bot
Copy link
Contributor

leha-bot commented Mar 6, 2023

Hello, @vitaut , is it able to make a new patch release with fix of #3189? (e.g., 9.1.1)?
It would be very convenient as this bug hurts if you use the package managers (like cpm, vcpkg).

Thanks for your attention.

@vitaut
Copy link
Contributor

vitaut commented Mar 12, 2023

Thanks for the suggestion but I don't think that change warrants a new release. The linked issue is actually misleading: the variable in question was set just in the {fmt} subdirectory and didn't affect the parent project which is easy to check. So it's more of a usability improvement that enables separate control of the standard version. In any case you could pin to a specific commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants