On Fri, Aug 3, 2012 at 1:00 PM, Michael Meeks <michael.meeks@suse.com> wrote:
I guess we'd want to do that build regularly; perhaps doing some
tweaking to make it part of Lubos' clang / tinderbox build might be a
good long-term solution ?
Hrm. On second thought, maybe we should wait to see if the reports are
actually investigated first, before we start working on a more
permanent and regularly updated system ? Permanent updated exports
arent really useful if nobody takes the time to investigate.
On Fri, Aug 3, 2012 at 1:28 PM, Olivier Hallot
<olivier.hallot@documentfoundation.org> wrote:
Like unusedcode.easy, your file could be placed in the git tree root and
updated periodically.
Well it's not a single file: it's 2 directories filled with annotated
source files. Also, all of it's HTML, so a web server would seem like
a more fitting solution for storing the reports.
Just my 2$
Regards,
John Smith
Context
Re: Static src analysis of LibreOffice · bfo
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.