Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1

Radek Doulík <rodo -AT- novell.com>
Tue, 15 Feb 2011 15:44:08 +0100

On Tue, 2011-02-15 at 12:30 +0100, Radek Doulík wrote:

Hi,

I would like to have EMF+ support fixed in 3.3. The following two
commits are needed to fix it on

libreoffice-3-3 (1 review needed)
libreoffice-3-3-1 (3 reviews needed)

branches.

http://cgit.freedesktop.org/libreoffice/libs-gui/commit/?id=7de8695f19626c764a4b43cfb30179525d9a5956
http://cgit.freedesktop.org/libreoffice/libs-core/commit/?id=229df81b920ddee5a1b057af75db7b293f88e3bd


http://cgit.freedesktop.org/libreoffice/libs-core/commit/?id=2d3672612fb4f4d47116578fd5d1e7fdf44df709

one more commit needed, which fixes problem with static variable.
(thanks Thorsten)

Cheers
Radek

Cheers
Radek


-- 
Radek Doulík <rodo@novell.com>
Novell, Inc.

Context

[Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Radek Doulík
- Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Jesús Corrius
  - Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Petr Mladek
- Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Radek Doulík
  - Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Michael Meeks
    - Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Tor Lillqvist
    - Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Radek Doulík
    - (message not available)
      - Re: [Libreoffice] [REVIEW] fix for EMF+ on 3-3 and 3-3-1 · Radek Doulík

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.