mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-03 03:28:09 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
05fc275837
Previously the matching logic was designed to match names like this ``` 99993681767ac...32132a.anv.mda.tar/CS/NIR8/046-ssa ``` So up until the first slash of a pattern, a prefix match would be used, followed by fuzzy matching for the remaining pattern. This don't work well when there are subdirectories in the name, so when we see ``` before/99993681767ac...32132a.anv.mda.tar/CS/NIR8/046-ssa before/91132154353bd...090919.anv.mda.tar/CS/NIR8/046-ssa after/91132154353bd...090919.anv.mda.tar/CS/NIR8/046-ssa ``` the first entry can't be matched by `before/9999/first` since the fuzzy match will kick in for the 9999 and if the second entry has four 9s (which it does here) there would be multiple choices. In practice the flexibility of fuzzy matching is not really needed since we've been using consistent small prefixes (like CS, NIR8, BRW, etc). The exception is the last part (the object versions, i.e. "pass names"), where sometimes is convenient to reach by a substring. The new matching logic is to use prefix match by default, except when matching the "object version", where substring match is used. In the example a possible set of the patterns to identify each entry can be `b/99/ssa`, `b/91/ssa` and `a/91/ssa`. The patch adds a few tests to the `is_match()` to clarify the behavior. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/39506> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| src | ||
| subprojects | ||
| .clang-format-ignore | ||
| .clang-format-include | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| clippy.toml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| VERSION | ||
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.