On 12/05/2010 12:39 PM, Caolán McNamara wrote:
All true. It was just a note that it might be easier, if you have an
interest in binfilter, to just take the conservative approach and
silence warnings with e.g converting
I was thinking of taking a 2 steps approach: first silent warning in a
conservative way (this is also less risk to introduce bugs) and then to
"down-size" the module just keeping the needed part.
In my opinion, the needed part would be, for the next releases, just the
read capability of (older?) binary format build in within LibO.
But if the decision is to drop it anyway for the next release, does not
bring a lot.... I did not found any inputs about it within mailing
lists. Has the point been discussed somewhere? Is this to be handle by
the steering committee? Is there a "technical" steering committee for
this kind of decision, where we could propose / give reasons for
thinking this or that? Currently, as said, I am doing conservative
warning fixes, but to start something more intrusive, would like to have
first a kind of direction decision.
regards
Context
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.