c8ef 2f53cdc885
[folly related] update to 05.02 (#38536)
<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->

<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->


- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [x] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [x] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.


<!-- If this PR adds a new port, please uncomment and fill out this
checklist:

- [ ] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] The name of the port matches an existing name for this component
on https://repology.org/ if possible, and/or is strongly associated with
that component on search engines.
- [ ] Optional dependencies are resolved in exactly one way. For
example, if the component is built with CMake, all `find_package` calls
are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or
disabled with
[CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html).
- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
- [ ] The license declaration in `vcpkg.json` matches what upstream
says.
- [ ] The installed as the "copyright" file matches what upstream says.
- [ ] The source code of the component installed comes from an
authoritative source.
- [ ] The generated "usage text" is accurate. See
[adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md)
for context.
- [ ] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [ ] Only one version is in the new port's versions file.
- [ ] Only one version is added to each modified port's versions file.

END OF NEW PORT CHECKLIST (delete this line) -->
2024-05-03 15:24:58 -07:00
..
2024-04-15 13:09:54 -04:00
2023-10-03 21:08:27 -07:00
2023-10-09 15:27:37 -07:00
2024-01-19 11:56:09 -08:00
2024-04-15 13:11:16 -04:00
2024-04-08 11:15:54 -07:00
2023-08-31 12:52:56 -07:00
2024-03-25 15:34:46 -07:00
2024-02-05 00:56:22 -08:00
2024-02-27 00:44:07 -08:00
2023-11-14 16:09:58 -08:00
2024-03-13 16:42:39 -07:00
2024-02-07 12:33:25 -08:00
2024-04-18 19:35:36 -04:00
2022-09-16 14:06:00 -07:00
2023-09-28 22:41:44 -07:00
2023-05-22 11:34:06 -07:00
2023-05-04 10:31:46 -07:00
2023-08-17 11:08:01 -07:00
2024-01-22 10:59:48 -08:00
2022-10-05 15:06:50 -07:00
2022-10-05 15:05:06 -07:00
2024-03-25 15:30:22 -07:00
2023-10-02 20:53:42 -07:00
2024-03-25 15:34:55 -07:00
2023-02-09 14:51:04 -08:00
2023-02-09 14:51:04 -08:00
2023-02-09 14:51:04 -08:00
2023-02-09 14:51:04 -08:00
2024-01-22 10:56:30 -08:00
2023-12-20 12:30:12 -08:00
2023-12-13 23:23:17 -08:00
2022-12-09 10:50:10 -08:00
2023-10-24 11:05:02 -07:00
2023-10-03 18:04:10 -07:00
2024-04-30 11:27:28 -07:00
2022-12-19 11:33:56 -08:00
2023-09-28 22:26:33 -07:00
2024-03-14 12:22:32 -07:00
2023-11-08 10:10:24 -08:00
2023-07-17 13:08:24 -07:00
2023-01-17 11:35:55 -08:00
2024-01-23 11:44:45 -08:00
2023-10-04 14:25:20 -07:00
2023-10-09 15:36:14 -07:00
2024-04-24 10:57:12 -04:00
2024-02-07 12:29:55 -08:00