[Libreoffice] [REVIEW-3-4] fix ole automation bridge handling of SAFEARRAY (fdo#38441)

Noel Power <nopower -AT- suse.com>
Wed, 26 Oct 2011 17:55:32 +0100

there were at least a few people trying to make this a blocker for 3.4 ( makes ole automation quite 
broken ), the fix on master I would like to backport is here

http://cgit.freedesktop.org/libreoffice/core/commit/?id=3fcb94311fd7dd40c05ca132e3a30a888316cbbe

Noel

Context

[Libreoffice] [REVIEW-3-4] fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Noel Power
- Re: [Libreoffice] [REVIEW-3-4] fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Michael Stahl
  - [Libreoffice] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Michael Meeks
    - Re: [Libreoffice] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Noel Power
      - Re: [Libreoffice] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Noel Power
    - Re: [Libreoffice] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Noel Power
      - Re: [Libreoffice] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Stephan Bergmann
        
        Re: [Libreoffice] [PUSHED-3-4-4] [REVIEW-3-4-4] )one more needed) fix ole automation bridge handling of SAFEARRAY (fdo#38441) · Thorsten Behrens

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.