Date: prev next · Thread: first prev next last
July 2025 Archives by date, by thread · List index


UBSAN Linux Build - Build # 3629 - Successful:


Check console output at https://ci.libreoffice.org/job/lo_ubsan/3629/ to view the results.

Changes for Build #3629
[Michael Weghorn] tdf#130857 qt weld: Support Calc "Go to Sheet" dialog

[Michael Weghorn] tdf#130857 qt weld: Convert accelerators for frame/group box

[Caolán McNamara] const up libwpd

[Markus Mohrhard] tdf#118668: handle wrong XLSX sheet visibility settings in line with

[Markus Mohrhard] tdf#164014: export value filters through the value property to ODS

[Noel Grandin] Drop separate EditTextObject itempool

[Mike Kaganski] tdf#143148: Use pragma once instead of include guards

[Noel Grandin] extract inner loop of ScOutputData::LayoutStrings into another func

[Noel Grandin] loplugin:blockblock

[Ilmari Lauhakangas] tdf#165233 replace std::bind with lambda in xmldataprovider.cxx

[Caolán McNamara] const up coinmp

[Markus Mohrhard] tdf#122336: handle OOXML files with invalid cell refs better

[Caolán McNamara] const up clew
-- 
To unsubscribe e-mail to: libreoffice-ci+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/libreoffice-ci/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.