Date: prev next · Thread: first prev next last
June 2022 Archives by date, by thread · List index


UBSAN Linux Build - Build # 2423 - Successful:


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

Changes for Build #2423
[gerrit buildbot] Update git submodules

[Julien Nabet] Fix typo

[Julien Nabet] Fix typos

[Luboš Luňák] make SfxStateCache::xDispatch up to date before using it

[Andreas Heinisch] tdf#149402 - BASIC: Don't extend comment if line ends in a whitespace

[Julien Nabet] Fix typos

[Noel Grandin] clang-tidy modernize-pass-by-value in accessibility

[Noel Grandin] clang-tidy modernize-pass-by-value in basctl

[Noel Grandin] add comments to SvtBroadcaster about field sizes/packing

[gerrit buildbot] Update git submodules

[Noel Grandin] improve field name

[Eike Rathke] Resolves: tdf#148163 Preserve names of bad cell reference input again

[Eike Rathke] ScSingleRefData::TabValid: for absolute reference take sheets into

[Eike Rathke] Resolves: tdf#147390 tag oc-FR to oc-FR-lengadoc, oc-ES to oc-ES-aranes

[gerrit buildbot] Update git submodules
-- 
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.