Re: [Libreoffice] [PATCH] [PUSHED] Replace j_assert with OSL_ in writer/starmath

Jacek Wolszczak <shutdownrunner -AT- gmail.com>
Fri, 18 Mar 2011 15:49:30 +0100

Yes, it is under LGPLv3+ / MPL.

Thanks.

Jacek

2011/3/18 Thomas Arnhold <thomas@arnhold.org>

Hi Jacek,

On 03/18/2011 09:14 AM, Jacek Wolszczak wrote:

I did compile it with --enable-debug as it's OSL_ specific and it
compiled correctly. Haven't used --enable-dbgutil as there are no #ifdef
DBG_UTIL in the files I touched.

But for the future I will recompile LibreO with both flags enabled.


I think this is ok as you did it. I'll push it in the afternoon. Thanks
for your patch.

Can you confirm that your patch is under  LGPLv3+ / MPL licence?

Thomas
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Context

[Libreoffice] [PATCH] Replace j_assert with OSL_ in writer/starmath · Jacek Wolszczak
- Re: [Libreoffice] [PATCH] Replace j_assert with OSL_ in writer/starmath · Thomas Arnhold
  - Re: [Libreoffice] [PATCH] Replace j_assert with OSL_ in writer/starmath · Jacek Wolszczak
    - Re: [Libreoffice] [PATCH] [PUSHED] Replace j_assert with OSL_ in writer/starmath · Thomas Arnhold
      - Re: [Libreoffice] [PATCH] [PUSHED] Replace j_assert with OSL_ in writer/starmath · Jacek Wolszczak
      - Re: [Libreoffice] [PATCH] [PUSHED] Replace j_assert with OSL_ in writer/starmath · Thomas Arnhold

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.