Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc

Maciej Rumianowski <maciej.rumianowski -AT- gmail.com>
Wed, 20 Jul 2011 23:24:24 +0200

Dnia 2011-07-20, śro o godzinie 17:12 -0400, Kohei Yoshida pisze:


So, I've reviewed your revised patches and they look good.  I've
pushed
them to master with one minor syntactic change.


Great thanks :)

Anyway, thanks for your patches again, and we look forward to
receiving
more patches from you in the future. :-)


I'm working further on Bug 38831 - [EasyHack] Get rid of SV_DECL_VARARR,
SV_DECL_VARARR_PLAIN, SV_DECL_VARARR_SORT ...

Where can I mark that I'm working on it? In Bug comments?

Best Regards,
        Maciej

Context

[Libreoffice] SfxIntegerListItem constructor used by DataPointItemConverter and SeriesOptionsItemConverter · Maciej Rumianowski
- [Libreoffice] [PATCH] Get rid of SvULongs in calc · Maciej Rumianowski
  - Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Maciej Rumianowski
    - Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Kohei Yoshida
      - Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Maciej Rumianowski
        
        Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Kohei Yoshida
        
        Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Maciej Rumianowski
        
        Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · Kohei Yoshida
        
        Re: [Libreoffice] [PATCH] Get rid of SvULongs in calc · David Tardon

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.