On Thu, Feb 22, 2024 at 10:24 AM Cristian Constantin via Wireshark-dev < wireshark-dev@wireshark.org> wrote:
> Hi, > How to figure out if a fix for an issue like the one mentioned by John > above is part of a Wireshark release? And what Wireshark release is > part of... > The Gitlab page for the commit has some entries that indicate which branches and tags (tags would indicate releases) have a commit. This one is only in the master branch, not a release. https://gitlab.com/wireshark/wireshark/-/commit/922d1f621935ace31d08243c2627c149111401be Some commits that fix bugs (as opposed to new features or performance enhancements) are backported. There will be links added in the merge request and the commits to other commits that were backported. That is not going to happen for this commit. John
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
